Compute network refactor #23
Commits on Feb 12, 2015
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Just try the first IP available if none found before
Some cloud don't implement correctly IP addresses. Instead of failing during the provisionning, we just take the first IP available and try with this one.
-
-
-
-
-
-
-
-
-
This commit renames image_ref to image_id and adds the image_name parameter. Users can now specify either an image UUID or image name when launching instances. image_name is preferrable as deployers/sysadmins generally regularly deprecate/remove outdated and insecure images. Using a consistent naming scheme allows end-users to always retrieve a working image.
-
Accounting for multiple results of an image name
If multiple results are found, an error will be returned to the user.
-
-
-
-
This commit renames flavor_ref to flavor_id and adds the flavor_name parameter. Users can now specify either a flavor ID or name when launching instances.
-
This commit enables both the image_id and the image_name to be
computed, so that specifying one will populate the other.
-
-
This commit adds the ability for instances to attach volumes from within their resource.
-
-
-
-
-
-
Merge pull request #9 from jtopjian/secgroup-fix
Changing how security groups are read for compute instances
Commits on Feb 13, 2015
-
-
This commit populates access_ip_v6 by either the AccessIPv6 attribute or by finding the first available IPv6 address. This commit retains the original feature of setting the default ssh connection to the IPv4 address unless one is not found. IPv6 access can still be enabled by explicitly setting it in the resource paramters. This commit also removes d.Set("host") in favor of SetConnInfo -
Merge pull request #5 from jtopjian/access-ip-v6
Added access_ip_v6 support
-
Merge pull request #10 from jtopjian/secgroup-rule-fix
Fixing rule/rules and re-arranged order for schema consistency
Commits on Feb 16, 2015
Commits on Feb 17, 2015
-
Merge pull request #15 from longnguyen11288/self-sg
Added self option to security groups
-
Replace perigee.UnexpectedResponseCodeError with gophercloud.Unexpect…
…edResponseCodeError
-
Merge pull request #16 from haklop/fix-UnexpectedResponseCodeError
Replace perigee.UnexpectedResponseCodeError with gophercloud.UnexpectedResponseCodeError
Commits on Feb 19, 2015
-
openstack_compute_floatingip_v2
This commit adds a resource that allows the user to allocate, deallocate, associate, and disassociate floating IPs through the nova api.
-
This commit ensures that a volume is detached from all instances before it is deleted. It also adds in an `attachment` exported parameter that shows details of the volume's attachment(s).
Commits on Feb 20, 2015
-
Merge pull request #11 from jtopjian/compute-floating-ip
openstack_compute_floatingip_v2
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
FWaaS version is actually v1 not v2
Rename files and methods. Confusion have been made between neutron version and FWaaS extension version.
-
-
-
-
Merge pull request #3 from ggiamarchi/fwaas
OpenStack Firewall as a Service
Commits on Feb 24, 2015
-
Merge pull request #17 from jtopjian/volume-safe-delete
Volume Safe Delete
Commits on Mar 4, 2015
-
-
Merge pull request #19 from jtopjian/secgroup-self-fix
Allows "self" to be discovered and recorded correctly.
Commits on Mar 13, 2015
-
This commit adds pending states for volume attachment, detachment, and deletion.
Commits on Mar 14, 2015
-
Merge pull request #20 from jtopjian/volume-pending-states
Volume Pending States
Commits on Mar 24, 2015
Commits on Mar 25, 2015
-
Merge pull request #24 from julienvey/general_comments
Fix general comments by @phinze
-
-
Merge pull request #22 from cbuben/openstack-gophercloud-v1.0-userdata
user_data support
Commits on Mar 26, 2015
-
This commit causes the resource to manage floating IPs by way of the os-floating-ips API. At the moment, it works with both nova-network and Neutron environments, but if you use multiple Neutron networks, the network that supports the floating IP must be listed first.
-
Removes check for a "public" network
This is only possible if the OpenStack cloud explicitly has a network called "public".
-
-
Allow networks to be specified by name
This commit allows the user to specify a network by name rather than just uuid. This is done via the os-tenant-networks api extension. This works for both neutron and nova-network.
-
This commit changes how the network info is read from OpenStack. It pulls all relevant information from server.Addresses and merges it with the available information from the networks parameters. The access_v4, access_v6, and floating IP information is then determined from the result. A MAC address parameter is also added since that information is available in server.Addresses.
-
-
-
-
Floating IPs and Neutron Network Ordering
This commit enables multiple neturon networks to be specified in any order. In order to attach a floating IP, the floating ip enabled neutron network must either be the first in the list or be tagged with "set_floating_ip" in the network block. Existing nova-network support is unchanged.
-