Skip to content
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

OpenStack named network enhancements #7

Merged
merged 9 commits into from
Mar 7, 2014
Merged

OpenStack named network enhancements #7

merged 9 commits into from
Mar 7, 2014

Commits on Feb 28, 2014

  1. notes on knife-openstack changes

    @mattray
    mattray committed Feb 28, 2014
    Configuration menu
    Copy the full SHA
    eeb088a View commit details
    Browse the repository at this point in the history

  2. separated current and future proposals

    @mattray
    mattray committed Feb 28, 2014
    Configuration menu
    Copy the full SHA
    8220121 View commit details
    Browse the repository at this point in the history

  3. Ohai 7 cloud network enhancements

    @mattray
    mattray committed Feb 28, 2014
    Configuration menu
    Copy the full SHA
    2052d62 View commit details
    Browse the repository at this point in the history

  4. add internal discussion link

    @mattray
    mattray committed Feb 28, 2014
    Configuration menu
    Copy the full SHA
    16d8084 View commit details
    Browse the repository at this point in the history

  5. ohai changes will be a separate PR

    @mattray
    mattray committed Feb 28, 2014
    Configuration menu
    Copy the full SHA
    fadc9b2 View commit details
    Browse the repository at this point in the history

  6. Add --no-network to the RFC 

    The comments in chef/knife-openstack#30 make the case
for not knowing the names of your networks in advance.
    @mattray
    mattray committed Feb 28, 2014
    Configuration menu
    Copy the full SHA
    b997912 View commit details
    Browse the repository at this point in the history

  7. Added --bootstrap-network 

    This was in the original internal RFC, I overlooked it thinking --networks
covered the use case. Clearly it is necessary.
    @mattray
    mattray committed Feb 28, 2014
    Configuration menu
    Copy the full SHA
    0e0267c View commit details
    Browse the repository at this point in the history

  8. Removed --network option because OpenStack API does not appear to sup… 

    …port it

Dug through the API code and server_create code in Fog and found that the
networks get attached to the node after server_create is called, which means
there's currently no abilility to limit which networks attached by new servers.
This could be a limitation of my test environment (nova-network), but the API
docs and Fog code appear to support this conclusion.
    @mattray
    mattray committed Feb 28, 2014
    Configuration menu
    Copy the full SHA
    a461ad1 View commit details
    Browse the repository at this point in the history

  9. link up KNIFE-423 for knife openstack network list

    @mattray
    mattray committed Feb 28, 2014
    Configuration menu
    Copy the full SHA
    14df1b4 View commit details
    Browse the repository at this point in the history