the function of create_test_server_group should be used instead
create_test_aggregate
Change-Id: I383bc563d369144a5f918064309b73e7984b61ab
Closes-Bug: #1736331
We should support to return a list of servers according to users' requirements.
In this patch, marker, limit, sort_key and sort_dir were added in server list
API.
- marker is used to display a list of servers after marker
- limit is used to determinate the maximum number of servers to display
- sort_key is used to sort the returned server list by specified key value
- sort_dir is used to select a sort direction
DocImpact
APIImpact
Change-Id: Id70e965794c82a0a29e53d4364f65b0f39042c7c
Closes-Bug: #1726665
Add the DB layer Operations for server tags
- set/unset server tags
- get server tags
- add/delete single tag
- check whether server tag exists
Change-Id: I2338ece8e4ae880835f6e20ef1e9e71a228a9703
Implements: blueprint server-tags-support
This field will indicate whether we should delete or unbind the
port during server deletion or detaching interfaces.
Change-Id: I25834a82b83806bf87b4c7006a8d33d56e2ce976
Closes-Bug: #1715040
Currently we support to list compute nodes and aggregate nodes
with names, but server show will return the node uuid always,
which make the admins have to go ironic to get the relationship
between name and uuid, so this changes to return node name.
Change-Id: Ia0e5122aa29c4de2e870c5b71c420de49530ba92
Closes-Bug: #1715036
This change will allow the scheduler to select nodes with specified server
group in schedule_hints.
Partially Implements: bp support-schedule-hints
Change-Id: Idecd5e5f470eee12de0088b2332874b43f9dae52
We should not delete flavors which is still used by some running
servers, as users will get confused if they can't get the details
of the server flavor.
Partially Implements: bp new-flavor
Change-Id: I2c89d1fdb5092426d14e55b723f1eeb392e3c7fe
The disabled field is intended to not allow new servers
created from that flavor, so this makes it happen.
Partially Implements: bp new-flavor
Change-Id: I7a3509cef6f5dea5c7d6eac63fbb179a9850daae
We should extract resources aggregates information from flavor,
and pass it to placement with resources filters.
Partially Implements: bp node-aggregate
Change-Id: I96eeb7ab6636fa241e7d82bbddad8d70791c1f43
This change add ServerGroup, ServerGroupPolicy and ServerGroupMember
models, and add several basic DB interfaces.
Partially Implements: bp server-group-api-extension
Change-Id: I86e17798718fc26e1fd6a1fe1c33ee408738b6da
This change ensure allocations of a rp being deleted firstly before the rp
deleted. And this change also avoid updating the inventory of a rp if the
rp(node) has already been consumed.
Change-Id: I507176834f8247d112c8e6d969656d1a4dded6d7
Introduce the quota management in keypair creation and deletion.
Change-Id: I8241b0bfb38a9c41b564df07a7799e4bc5438c0d
Implements: blueprint quota-support
This addes aggregates db model with migrations and the related
API.
Partially Implements: bp node-aggregate
Change-Id: I019a9a4a5483750dc42a8cbf714a9d194d37fae8
This change clean the compute_node and compute_port versioned object
implementation and them db interfaces, after we totally switch to use
placement, we don't need to store any node info in Mogan's db.
Partially Implements: bp track-resources-using-placement
Change-Id: I515674d17a85a77a9380a60ef918dc6dbda8ed83
Currently, the port is not removed correctly when plug vif failed，
So we should fix it.
Change-Id: I095f0c3cc8fa281beb494a19f25cc20774df21f2
Closes-Bug: #1700437
This reverts commit 4b3a7dc31c.
We don't have a disks notion in mogan yet, and there's not a plan for
support it in Pike release, so get rid of it in case of making users
confusion.
Change-Id: I84a4dec001e68b9ef9a597389136587d18a45e39
The `disabled` field is intended to be used when phasing out
flavors. In this case, a delete wouldn't work because the flavor
needs to still be available for live servers using that flavor,
but we don't want to allow *new* servers created from that flavor.
Partially Implements: bp new-flavor
Change-Id: I12713bfe13f506a0d9bb79f733b00bd637ef227b
This removes flavor extra specs table and related methods,
moving extra specs to flavor table to make things simple,
as we have already changed to use flavor PATCH method to
manage such things.
Change-Id: I1fb5445b7d194b50b052b77624a70e59af547911
When create a baremetal server, it will trigger rescheduler task if failure.
But it will not clearup some remaining info in the previous create_server
taskflow, such as network_info of the server. And server.node_uuid will be
cleaned if not do rescheduler, which we don't expect.
Change-Id: I25ab763ec8dd6b1ddaf66132216f285cfd73d1c1
Closes-Bug: #1691311
This removes nodes cache and turn to use resources saved in DB.
A following up patch will split scheduler out from engine service.
Change-Id: I89dea92b85ce7055accd3658aabe3a168ebe2df5
liuluyang