summaryrefslogtreecommitdiff
path: root/releasenotes/notes
Commit message (Collapse)AuthorAgeFilesLines
* Add release note for the vendor data regressionMonty Taylor2018-05-201-0/+5
| | | | Change-Id: Ifde1f9b51f0c40d386d655d2c44492664438eb6c
* Replace guts with openstack.config1.31.0Monty Taylor2018-04-271-0/+13
| | | | | | | | | | | | | | | | | | | The code has been moved into openstacksdk. Make os-client-config a thin wrapper around that code. The legacy client code needs to stay, as it was removed in openstacksdk. We also have to plumb os_client_config.defaults and os_client_config.cloud_region.CloudRegion in so that users get the os-client-config versions from the openstacksdk methods that return the relevant objects. Support for per-service region_name has been dropped. This was never used anywhere and was added for compatibility with openstacksdk Profile objects. Since Profile objects are no more, we can remove it. It never made any sense. Change-Id: I7180e20aa675c0ccbe3718493a6eff2be7e1b8b6
* Add Limestone Networks vendor infoLogan V2018-03-291-0/+4
| | | | | | | Adds the Limestone Networks provider info for the Dallas and Salt Lake regions. Change-Id: Id457ea68938aea955162dc42a112568b2e55b850
* Add betacloud to the vendorsChristian Berendt2017-12-111-0/+3
| | | | Change-Id: I599156ee4e2ff52e4db5669fce6cacd22447c3b0
* Added nat_source flag for networks.Monty Taylor2017-10-211-0/+6
| | | | | | | | | In some more complex clouds there can not only be more than one valid network on a server that NAT can attach to, there can also be more than one valid network from which to get a NAT address. Allow flagging a network so that it can be found. Change-Id: I3d8dd6d734a1013d2d4a43e11c3538c3a345820b
* Merge "Update make_rest_client to work with version discovery"Zuul2017-10-211-0/+6
|\
| * Update make_rest_client to work with version discoveryMonty Taylor2017-10-181-0/+6
| | | | | | | | | | | | | | | | | | | | Using make_rest_client on clouds that put unversioned endpoints in the catalog results in incorrectly set up adapters. Add the plumbing to get_session_client to pass version args to keystoneauth. Then use that from make_rest_client. Change-Id: I69ad746f672ef0b12680e9db3c7b0c691c9f87e4
* | Treat clouds.yaml with one cloud like envvarsMonty Taylor2017-09-191-0/+7
|/ | | | | | | | | If there is only one cloud and that cloud is envvars, things work as expected. If there is only one cloud in clouds.yaml and no envvars cloud, we throw an error, even though it should be obvious which cloud was intended. Change-Id: Ia49d0fb2cc7dca36476d0e5ae3fe2b2aa1209e59
* Fix interactions with keystoneauth from newtonMonty Taylor2017-04-281-0/+7
| | | | | | | | | keystoneauth in newton did not have app_name or app_version as Session parameters. Although it isn't a super common combination, user agent strings aren't a reason to break something. Add a simple workaround. Change-Id: Ib5774389fefdbc190a4b78dd6784c8006afbb270
* Add support for bailing on invalid service versionsMonty Taylor2017-03-091-0/+15
| | | | | | | | | | | | | | | | | At least for cinder for now, allow a consumer of get_legacy_client to express the minimum version they find acceptable. This will use cinder_client logic to figure out the version from the url. As a follow on, expand this to all of the clients and make it support microversions for the clients that support microversions. (Right now it's just going to be major versions, so min_version=1 will throw an exception if the cinder service returns a v1 endpoint. Also, because we override the volume/volumev2/volumev3 service type stuff, we need to do extra special logic in get_session_endpoint to try all three in the case where do not have a configured api_version. Change-Id: I7b6b3588fec9a6be892cf20d344667f0b9a62f0a
* Pass ironic microversion through from api_versionMonty Taylor2017-02-281-0/+4
| | | | | | | | If someone sets baremetal_api_version to 1.29 right now, we don't really do anything with that information. Pass it through to the constructor for ironicclient in get_legacy_client(). Change-Id: I470fbb8852eac7d5cb35aef549ac591d63f3636f
* Add ability to skip yaml loadingMonty Taylor2017-02-271-0/+7
| | | | | | | | | | Added a flag, 'load_yaml_config' that defaults to True. If set to false, no clouds.yaml files will be loaded. This is beneficial if os-client-config wants to be used inside of a service where end-user clouds.yaml files would make things more confusing. Change-Id: Idbc82bb931e9edf1bbcc575237c0e202e219c218
* Add release notes for 1.19.0 releaseDean Troyer2016-08-034-0/+23
| | | | Change-Id: I92ffcf611d31f7a4f11e5228022ea64864823389
* Add shade constructor helper methodMonty Taylor2016-06-021-0/+4
| | | | | | | | | We have helper factory methods for REST Client, legacy client and OpenStack SDK all with the same interface ... we might as well have one for shade too. It makes documenting and talking about the simple case of all of them easy. Change-Id: I046da85ae4a3e2a6333223921d5ae9ce3673121d
* Rename session_client to make_rest_clientMonty Taylor2016-06-011-0/+4
| | | | | | | | | | While writing some docs, it became clear that session_client was just a horrible horrible name and that I'm a bad person. Rename it so that we can make docs that make humans happy. Also, move the REST client section of the README up a bit. Change-Id: I1a27853e3031489da5916308a76f19bc72185d24
* Add helper method for OpenStack SDK constructorMonty Taylor2016-06-011-0/+4
| | | | | | | | openstacksdk already has a helper method for dealing with occ, but if a user is already using the occ helper methods, there is no reason we should not provide them an easy path to using the SDK. Change-Id: I1040efb94385fdac0aa02ac960ba95089b954377
* Flesh out netowrk config listMonty Taylor2016-04-021-3/+2
| | | | | | | | Add support for indicating default_interface. Also, add some validation and normalization code, some interface methods and, shockingly, documentation. Change-Id: Ib45b68894585ac02821d5d2376510fd7a8e8ee40
* Change network info indication to a generic listMonty Taylor2016-03-301-0/+11
| | | | | | | | | | | Networks can have more information than just internal or external. Notably, if you have two private networks and you're trying to assign floating ips, you need to know which network should be the recipient. This should be backwards compatible with existing external_network and internal_network options. Change-Id: I0d469339ba00486683fcd3ce2995002fa0a576d1
* Allow session_client to take the same args as make_clientMonty Taylor2016-02-221-0/+6
| | | | | | | | | | | | | | | make_client is a great, simple yet flexible way to get a fully featured Client object. simple_client is similar for Session objects, but lacks the argparse and arbitrary kwargs that make_client - plus it has a weird name. Since adding those two features to make_client did not make it too confusing - do the same for simple_client. Also, rename it to session_client (with a backwards-compat alias) and add it to the README docs. In the process of doing this, extract the "get me a cloud config" functinality into an additional helper function - get_config. Change-Id: Iadd24dfa021f870b3e5858bab8cd91fc96a373c2
* Add release notes1.15.0Clark Boylan2016-02-171-0/+22
| | | | | | | Catch up the release notes from the previous release to current state. This does not catch up from the beginning of oscc's history. Change-Id: Ic981fdfbb79cd7fc70167091bdfed281c11eff03
* Use reno for release notesMonty Taylor2015-12-301-0/+3
The OpenStack Release team has created a great release notes management tool that integrates with Sphinx. Start using it. For reference on how to use it, see http://docs.openstack.org/developer/reno/ Change-Id: I8153ec7861b508297a28a1916771776dee2deafe
View Lorry Controller Status