Commit Graph

11 Commits

Author SHA1 Message Date
Michal Nasiadka bc79012f46 Drop Swarm support
Label validator function has been left behind, although it's not
checking for anything right now - might be useful in future.

Change-Id: I74c744dc957d73aef7556aff00837611dadbada7
2024-01-24 13:20:21 +13:00
guilhermesteinmuller 6e8657912c Drop Mesos code
The coe mesos has not been maintained for quite some
time and hasn't got much attention from the community
in general. As discussed in the mailing list [1] we
are dropping for now.

[1] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026230.html

Co-Authored-By: jake.yip@ardc.edu.au

Change-Id: Ie7de9a37bfad6214f52d0605409e74d62a51df47
2023-03-07 14:02:05 +11:00
Feilong Wang d80febb384 Add health_status and health_status_reason to cluster
APIImpact
Related blueprint cluster-healing

Change-Id: I78d4d14fb064996de77bdd6a381d2df53a9488b8
2018-08-27 14:28:46 +12:00
yatin 745188b5ef Restrict server type only to vm/bm
Currently server type can be set to any String, but it should
be restricted to only allowed types: vm/bm.
vm: virtual machine
bm: baremetal
With this patch it is restricted only to allowed types.

Change-Id: Ifbeff8621b26702e54ad088195fddcb7c35424b2
Closes-Bug: #1622432
2016-09-16 14:48:44 +05:30
Jenkins 5f78e2f33a Merge "Restrict magnum service name" 2016-09-16 08:09:15 +00:00
Jaycen Grant 729c2d0ab4 Rename Bay DB, Object, and internal usage to Cluster
This is patch 3 of 3 to change the internal usage of the terms
Bay and BayModel.  This patch updates Bay to Cluster in DB and
Object as well as all the usages.  No functionality should be
changed by this patch, just naming and db updates.

Change-Id: Ife04b0f944ded03ca932d70e09e6766d09cf5d9f
Implements: blueprint rename-bay-to-cluster
2016-09-08 13:01:12 -07:00
Rajiv Kumar fd05c590a5 Restrict magnum service name
Magnum service binary name can be only conductor. Currently any
string having length less than 256 is allowed.

Change-Id: I03dad7a36a01e22e5fc63917f5e2919636f6ab2f
Closes-bug: #1615221
2016-08-22 09:30:31 +05:30
space 36a6fde15a Add more types of status to Bay's status
Added more types of status which can be updated to Bay's status field:
'RESUME_COMPLETE'
'RESTORE_COMPLETE'
'ROLLBACK_COMPLETE'
'SNAPSHOT_COMPLETE'
'CHECK_COMPLETE'
Added these states so that the bay_update code have better resiliency
If the user operates the stack,he(she) could still update the bay.

Change-Id: Ia71ca90742a7e23bbf2c0c9254951db7e06faf28
Closes-Bug: #1538447
2016-02-02 12:50:43 +08:00
Hongbin Lu 618f019f4d Introduce BayType that declares valid COEs
Restrict COE field to be one of 'kubernetes', 'swarm' and 'mesos'

Change-Id: I8967b1cd826c8c22fa5c1d847776e5e0dd65c629
Closes-Bug: #1497134
2015-09-28 15:55:40 -04:00
Ryan Rossiter 5ac2dce563 Add field for container status
This adds an enum for the different statuses and changes over to use
those constants in docker conducter.

An UNKNOWN value was also added because the API tests expected 'Unknown'
so this value needed to be added to the field in order to be valid.

Change-Id: Ic79317f0fbdaf99c1979d3023f04c4eba44b412a
Closes-Bug: #1489136
2015-08-28 19:00:18 +00:00
Cale Rath e4add16a69 Use oslo.versionedobjects enums instead of status strings
Statuses are currently defined as a StringField when they should
be defined as an Enum object.  This fix changes these objects from
using StringField by extending the Enum object in
oslo.versionedobjects

Change-Id: I12760e1d72f4af9931ee97bbad298f92f785118f
Partial-Bug: #1489136
2015-08-27 15:55:02 +00:00