New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clustering is needed for creating a device service group cluster of multiple BigIPs #400

Closed

pjbreaux opened this issue May 11, 2016 · 2 comments

Assignees

Labels

enhancement feature request functional test unit test

Contributor

pjbreaux commented May 11, 2016

We need this feature for several customers. Given multiple BigIP objects, the cluster will perform the following operations:

Make the BigIPs trusted peers of one another in preparation for clustering
Create a device service group (or device group in the SDK) to sync failover objects
Ensure each BigIP device is in the state that we expect it to be in after the previous steps

pjbreaux self-assigned this

pjbreaux added enhancement feature request unit test functional test labels

pjbreaux pushed a commit to pjbreaux/f5-common-python-1 that referenced this issue


          Adding the cluster_manager module

720ea32

Issues:
Fixes F5Networks#400

Problem:
Initial commit for cluster_manager module for managing a BigIP cluster

Analysis:
Initial commit is using one large module to do all of the heavy lifting.
Will break out in future commits when common functionality arises

Tests:
Only manual tests so far

pjbreaux pushed a commit to pjbreaux/f5-common-python-1 that referenced this issue


          Adding device group manager

1d6431f

Issues:
Fixes F5Networks#400

Problem:
For clustering, we need to break apart the large cluster_manager module
into something less Blob(ish)

Analysis:
Broke apart similar functionality for checking/managing the device group
into a new module, the device_group_manager

Tests:
All manual tests still

pjbreaux pushed a commit to pjbreaux/f5-common-python-1 that referenced this issue


          Cluster refactors to created trusted_peer_manager.

bc6417e

Issues:
Fixes F5Networks#400

Problem:
Structure of clustering needs some refactoring and some testing

Analysis:
Moved the cluster modules into a cluster/ directory under f5. Also
created some functional tests for these features. So we have something
to hold onto.

Tests:
Three func tests exists now. The idea is that we can create, scale up,
scale down, and teardown a cluster. We do this with a sync-failover and
sync-only cluster type and then we create a cluster, only to delete the
cluster_manager object, reinitialize with the same devices, then
teardown that existing cluster.

pjbreaux pushed a commit to pjbreaux/f5-common-python-1 that referenced this issue


          Adding the cluster_manager module

ed938aa

Issues:
Fixes F5Networks#400

Problem:
Initial commit for cluster_manager module for managing a BigIP cluster

Analysis:
Initial commit is using one large module to do all of the heavy lifting.
Will break out in future commits when common functionality arises

Tests:
Only manual tests so far

pjbreaux pushed a commit to pjbreaux/f5-common-python-1 that referenced this issue


          Adding device group manager

2f65785

Issues:
Fixes F5Networks#400

Problem:
For clustering, we need to break apart the large cluster_manager module
into something less Blob(ish)

Analysis:
Broke apart similar functionality for checking/managing the device group
into a new module, the device_group_manager

Tests:
All manual tests still

pjbreaux pushed a commit to pjbreaux/f5-common-python-1 that referenced this issue


          Cluster refactors to created trusted_peer_manager.

79bf2ab

Issues:
Fixes F5Networks#400

Problem:
Structure of clustering needs some refactoring and some testing

Analysis:
Moved the cluster modules into a cluster/ directory under f5. Also
created some functional tests for these features. So we have something
to hold onto.

Tests:
Three func tests exists now. The idea is that we can create, scale up,
scale down, and teardown a cluster. We do this with a sync-failover and
sync-only cluster type and then we create a cluster, only to delete the
cluster_manager object, reinitialize with the same devices, then
teardown that existing cluster.

pjbreaux pushed a commit to pjbreaux/f5-common-python-1 that referenced this issue


          Adding the cluster_manager module

241658c

Issues:
Fixes F5Networks#400

Problem:
Initial commit for cluster_manager module for managing a BigIP cluster

Analysis:
Initial commit is using one large module to do all of the heavy lifting.
Will break out in future commits when common functionality arises

Tests:
Only manual tests so far

pjbreaux pushed a commit to pjbreaux/f5-common-python-1 that referenced this issue


          Adding device group manager

95fe02f

Issues:
Fixes F5Networks#400

Problem:
For clustering, we need to break apart the large cluster_manager module
into something less Blob(ish)

Analysis:
Broke apart similar functionality for checking/managing the device group
into a new module, the device_group_manager

Tests:
All manual tests still

pjbreaux pushed a commit to pjbreaux/f5-common-python-1 that referenced this issue


          Cluster refactors to created trusted_peer_manager.

Issues:
Fixes F5Networks#400

Problem:
Structure of clustering needs some refactoring and some testing

Analysis:
Moved the cluster modules into a cluster/ directory under f5. Also
created some functional tests for these features. So we have something
to hold onto.

Tests:
Three func tests exists now. The idea is that we can create, scale up,
scale down, and teardown a cluster. We do this with a sync-failover and
sync-only cluster type and then we create a cluster, only to delete the
cluster_manager object, reinitialize with the same devices, then
teardown that existing cluster.

pjbreaux pushed a commit to pjbreaux/f5-common-python-1 that referenced this issue


          Adding the cluster_manager module

fb0e19d

Issues:
Fixes F5Networks#400

Problem:
Initial commit for cluster_manager module for managing a BigIP cluster

Analysis:
Initial commit is using one large module to do all of the heavy lifting.
Will break out in future commits when common functionality arises

Tests:
Only manual tests so far

pjbreaux pushed a commit to pjbreaux/f5-common-python-1 that referenced this issue


          Adding device group manager

300e615

Issues:
Fixes F5Networks#400

Problem:
For clustering, we need to break apart the large cluster_manager module
into something less Blob(ish)

Analysis:
Broke apart similar functionality for checking/managing the device group
into a new module, the device_group_manager

Tests:
All manual tests still

pjbreaux pushed a commit to pjbreaux/f5-common-python-1 that referenced this issue


          Cluster refactors to created trusted_peer_manager.

3be70f5

Issues:
Fixes F5Networks#400

Problem:
Structure of clustering needs some refactoring and some testing

Analysis:
Moved the cluster modules into a cluster/ directory under f5. Also
created some functional tests for these features. So we have something
to hold onto.

Tests:
Three func tests exists now. The idea is that we can create, scale up,
scale down, and teardown a cluster. We do this with a sync-failover and
sync-only cluster type and then we create a cluster, only to delete the
cluster_manager object, reinitialize with the same devices, then
teardown that existing cluster.

pjbreaux pushed a commit to pjbreaux/f5-common-python-1 that referenced this issue


          Adding the cluster_manager module

4d45a73

Issues:
Fixes F5Networks#400

Problem:
Initial commit for cluster_manager module for managing a BigIP cluster

Analysis:
Initial commit is using one large module to do all of the heavy lifting.
Will break out in future commits when common functionality arises

Tests:
Only manual tests so far

pjbreaux pushed a commit to pjbreaux/f5-common-python-1 that referenced this issue


          Adding device group manager

19abd07

Issues:
Fixes F5Networks#400

Problem:
For clustering, we need to break apart the large cluster_manager module
into something less Blob(ish)

Analysis:
Broke apart similar functionality for checking/managing the device group
into a new module, the device_group_manager

Tests:
All manual tests still

pjbreaux pushed a commit to pjbreaux/f5-common-python-1 that referenced this issue


          Cluster refactors to created trusted_peer_manager.

c4e8c4d

Issues:
Fixes F5Networks#400

Problem:
Structure of clustering needs some refactoring and some testing

Analysis:
Moved the cluster modules into a cluster/ directory under f5. Also
created some functional tests for these features. So we have something
to hold onto.

Tests:
Three func tests exists now. The idea is that we can create, scale up,
scale down, and teardown a cluster. We do this with a sync-failover and
sync-only cluster type and then we create a cluster, only to delete the
cluster_manager object, reinitialize with the same devices, then
teardown that existing cluster.

This was referenced May 19, 2016

Refactor cluster.py #208

Closed

cluster_generic.py from f5-openstack-onboard should be ported to this repo and refactored #209

Closed

Failure in scaling up cluster with already added BIGIP #416

Closed

Contributor

wojtek0806 commented May 19, 2016

Issue Review: This looks like progressing. The mentioned issues could be folded into this one

Contributor

zancas commented May 19, 2016

Please see #208 for some relevant information.

pjbreaux pushed a commit to pjbreaux/f5-common-python-1 that referenced this issue


          Adding the cluster_manager module

2529d1d

Issues:
Fixes F5Networks#400

Problem:
Initial commit for cluster_manager module for managing a BigIP cluster

Analysis:
Initial commit is using one large module to do all of the heavy lifting.
Will break out in future commits when common functionality arises

Tests:
Only manual tests so far

pjbreaux pushed a commit to pjbreaux/f5-common-python-1 that referenced this issue


          Adding device group manager

1c2b439

Issues:
Fixes F5Networks#400

Problem:
For clustering, we need to break apart the large cluster_manager module
into something less Blob(ish)

Analysis:
Broke apart similar functionality for checking/managing the device group
into a new module, the device_group_manager

Tests:
All manual tests still

pjbreaux pushed a commit to pjbreaux/f5-common-python-1 that referenced this issue


          Cluster refactors to created trusted_peer_manager.

278b1f8

Issues:
Fixes F5Networks#400

Problem:
Structure of clustering needs some refactoring and some testing

Analysis:
Moved the cluster modules into a cluster/ directory under f5. Also
created some functional tests for these features. So we have something
to hold onto.

Tests:
Three func tests exists now. The idea is that we can create, scale up,
scale down, and teardown a cluster. We do this with a sync-failover and
sync-only cluster type and then we create a cluster, only to delete the
cluster_manager object, reinitialize with the same devices, then
teardown that existing cluster.

pjbreaux pushed a commit to pjbreaux/f5-common-python-1 that referenced this issue


          Adding device group manager

d28f50c

Issues:
Fixes F5Networks#400

Problem:
For clustering, we need to break apart the large cluster_manager module
into something less Blob(ish)

Analysis:
Broke apart similar functionality for checking/managing the device group
into a new module, the device_group_manager

Tests:
All manual tests still

pjbreaux pushed a commit to pjbreaux/f5-common-python-1 that referenced this issue


          Cluster refactors to created trusted_peer_manager.

0b09309

Issues:
Fixes F5Networks#400

Problem:
Structure of clustering needs some refactoring and some testing

Analysis:
Moved the cluster modules into a cluster/ directory under f5. Also
created some functional tests for these features. So we have something
to hold onto.

Tests:
Three func tests exists now. The idea is that we can create, scale up,
scale down, and teardown a cluster. We do this with a sync-failover and
sync-only cluster type and then we create a cluster, only to delete the
cluster_manager object, reinitialize with the same devices, then
teardown that existing cluster.

pjbreaux pushed a commit to pjbreaux/f5-common-python-1 that referenced this issue


          Refactor clustering as part of review with @zancas

7c0d9f2

Issues:
Fixes F5Networks#400

Problem:
Clustering is needed for creating a device service group cluster of
multiple bigip devices

Analysis:
This is part of a refactor from a code review that happened offline. It
was suggested to refactor the external interface that previously
existed with the Cluster class into ClusterManager, TrustDomain, and
DeviceGroup classes, which maintain state for their respective
operations and data. The interfaces presented by each of the classes
above are as uniform as possible, and allow for the ClusterManager to
manage the DeviceGroup and TrustDomain with ease.

Tests:
All previous unit tests and functional tests have been refactored or
rewritten in some way. All tests are currently passing.

zancas closed this as completed in

9f16243

pjbreaux pushed a commit that referenced this issue


          Adding the cluster_manager module

f15b3fb

Issues:
Fixes #400

Problem:
Initial commit for cluster_manager module for managing a BigIP cluster

Analysis:
Initial commit is using one large module to do all of the heavy lifting.
Will break out in future commits when common functionality arises

Tests:
Only manual tests so far

pjbreaux pushed a commit that referenced this issue


          Adding device group manager

555fea5

Issues:
Fixes #400

Problem:
For clustering, we need to break apart the large cluster_manager module
into something less Blob(ish)

Analysis:
Broke apart similar functionality for checking/managing the device group
into a new module, the device_group_manager

Tests:
All manual tests still

pjbreaux pushed a commit that referenced this issue


          Cluster refactors to created trusted_peer_manager.

55bb818

Issues:
Fixes #400

Problem:
Structure of clustering needs some refactoring and some testing

Analysis:
Moved the cluster modules into a cluster/ directory under f5. Also
created some functional tests for these features. So we have something
to hold onto.

Tests:
Three func tests exists now. The idea is that we can create, scale up,
scale down, and teardown a cluster. We do this with a sync-failover and
sync-only cluster type and then we create a cluster, only to delete the
cluster_manager object, reinitialize with the same devices, then
teardown that existing cluster.

pjbreaux pushed a commit that referenced this issue


          Refactor clustering as part of review with @zancas

732f3ef

Issues:
Fixes #400

Problem:
Clustering is needed for creating a device service group cluster of
multiple bigip devices

Analysis:
This is part of a refactor from a code review that happened offline. It
was suggested to refactor the external interface that previously
existed with the Cluster class into ClusterManager, TrustDomain, and
DeviceGroup classes, which maintain state for their respective
operations and data. The interfaces presented by each of the classes
above are as uniform as possible, and allow for the ClusterManager to
manage the DeviceGroup and TrustDomain with ease.

Tests:
All previous unit tests and functional tests have been refactored or
rewritten in some way. All tests are currently passing.

caphrim007 pushed a commit to caphrim007/f5-common-python that referenced this issue


          Adding the cluster_manager module

98d8485

Issues:
Fixes F5Networks#400

Problem:
Initial commit for cluster_manager module for managing a BigIP cluster

Analysis:
Initial commit is using one large module to do all of the heavy lifting.
Will break out in future commits when common functionality arises

Tests:
Only manual tests so far

caphrim007 pushed a commit to caphrim007/f5-common-python that referenced this issue


          Adding device group manager

8bb2658

Issues:
Fixes F5Networks#400

Problem:
For clustering, we need to break apart the large cluster_manager module
into something less Blob(ish)

Analysis:
Broke apart similar functionality for checking/managing the device group
into a new module, the device_group_manager

Tests:
All manual tests still

caphrim007 pushed a commit to caphrim007/f5-common-python that referenced this issue


          Cluster refactors to created trusted_peer_manager.

aaef80b

Issues:
Fixes F5Networks#400

Problem:
Structure of clustering needs some refactoring and some testing

Analysis:
Moved the cluster modules into a cluster/ directory under f5. Also
created some functional tests for these features. So we have something
to hold onto.

Tests:
Three func tests exists now. The idea is that we can create, scale up,
scale down, and teardown a cluster. We do this with a sync-failover and
sync-only cluster type and then we create a cluster, only to delete the
cluster_manager object, reinitialize with the same devices, then
teardown that existing cluster.

caphrim007 pushed a commit to caphrim007/f5-common-python that referenced this issue


          Refactor clustering as part of review with @zancas

99b68e1

Issues:
Fixes F5Networks#400

Problem:
Clustering is needed for creating a device service group cluster of
multiple bigip devices

Analysis:
This is part of a refactor from a code review that happened offline. It
was suggested to refactor the external interface that previously
existed with the Cluster class into ClusterManager, TrustDomain, and
DeviceGroup classes, which maintain state for their respective
operations and data. The interfaces presented by each of the classes
above are as uniform as possible, and allow for the ClusterManager to
manage the DeviceGroup and TrustDomain with ease.

Tests:
All previous unit tests and functional tests have been refactored or
rewritten in some way. All tests are currently passing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment