This updates all references of let(:chef_run) to cached(:chef_run) to
speed up tests. By doing this, we have to create a new cached(:chef_run)
block whenever we need to adjust node attributes for testing.
Additional fixes:
- Pull in openstack-network::ml2_core_plugin in server spec so that we get the
default attributes set
- Remove unused shared_examples
Speed was improved from 4 minutes 18.7 seconds to 1 minute 2.73 seconds
Change-Id: Ib10a6828e6886a57527a5e5a506cc57364ec0c2a
fog-openstack-1.x already appends "auth/tokens" so we no longer need to
do that. In addition, comment out endpoint type until this PR [1] gets
merged and released.
[1] https://github.com/fog/fog-openstack/pull/494
Depends-On: https://review.opendev.org/666176
Change-Id: Icc92d6c8eb868efbde904e6aeb9d36891ea8457a
Signed-off-by: Lance Albertson <lance@osuosl.org>
This patch removes the openstack_user resource with :grant_domain
action. A user is always created within a specific domain; such a
membership cannot be tacked on later. This resource gave the user the
role intended for their project for the domain (i.e., for the Default
domain instead of for the service project).
We add the domain_name attribute that creates the neutron user in the
desired domain. Note that this change needs a sufficiently recent
openstackclient cookbook -- otherwise the domain_name attribute is
ignored (which does not matter as long as the neutron user is to be
created in the Default domain).
Change-Id: I4b67565c9408c758acefc681dd756a1dca836ec3
This patch removes the role_name when using openstack_user's :create
action (it gets ignored by the target method).
Note that the spec test would still pass if only the line in
identity_registration.rb (but not the test) were changed, because the
code that actually does grant the role to the resource is executed right
after user creation and before any tests check the resource for the
existence of the role_name attribute. In other words: if the argument
were required in a call but only supplied in another call, the spec
tests would not catch it. Something to watch out for.
Change-Id: I9061b748281910bef3927757bdf22edfd36b7448
- Switched default linter to cookstyle
- Renamed rake tasks to better conform with Chef conventions
Change-Id: I5dd1971392fdf282d0f214dfce9dcbecc18542a8
- Now use cookbook-openstackclient to create endpoints role service and
user
- added domain creation and access granting
- added values to work with identity_v3
- rewrote specs to work again
- updated readme
- updated neutron-package dependencies for debian
Change-Id: I2d404a424bd79a6e9b282304e21591fa33a48981
Depends-On: I0f8955f05de9b33711c54b9a198f45018cceb8e1
* endpoint type (admin, internal, public) and service (identitiy, network etc.)
was switched during refactoring, this patch reverts this unintended switching
* edited bind_service service type from public,internal,admin to 'all'
for default binding to just one service
Change-Id: I9bf230ba53d23ce11a32acaea2410572eaeb6123
Depends-On: Iec485deaf415e4187a323435cce2b6bbadfc5d42
Depends-On: Ia5bddfc5e2fd77cd6e9e855c680b079f78fc1c3f
* added new logic to render plugin templates
* refactored recipe names to be more consistence
* moved version up to 13.0.0 for mitaka release
* removed suse as supported platform
* added verisionbumb for refactored os-identity and common
* adapted optimized endpoint logic
* added endpoint attributes to fit new endpoint logic
* adapted the specs (unit tests) to work again
* refactored attributes throughout all recipes that were connected to the
attributes used for the neutron.conf.erb template to adapt the new template
attribute syntax
* removed some attributes that were set to non default values, since the
defaults from neutron cloud and should be used instead
* moved all attributes form attributes/default.rb that were used in
neutron.conf.erb to attributes/neutron_conf.rb
* refactored attributes to fit new template logic
* refactored recipes/default.rb to fit new template logic
* removed all attributes set to default values in attribtues/default and
template
* replaced static plugin logic and templates with new config logic, following
the same principles as for neutron.conf
* renamed recipes to fit attributes and actual service names
* added recipes for ml2_core_plugin, ml2_openvswitch and ml2_linuxbridge as well
as a recipe for the creation of all plugin configs (plugin_conf) like plugin.ini
Change-Id: I9cc1b5cc069987ac83e064322c2291772505ff5f
Implements: blueprint cookbook-refactoring
Depends-On: I0547182085eed91d05384fdd7734408a839a9a2c
Depends-On: I3262b2e6f792f37c32a446e6567790b82bdd4613
- deprecated Gemfile
- updated TESTING and README
- updated Rakefile to use chef exec instead of bundle exec
- replaced Runner by SoloRunner in specs
Change-Id: Ic99092a33eeaa57dc7083c892bca729735bebdf7
Now that admin_endpoint, public_endpoint, and internal_endpoint
in the common library are working, these are the changes to use
them in the openstack-network recipes.
Note that some calls to 'endpoint' that can't have separate
admin, internal, public endpoints. (E.g. network-api-bind,
network-linuxbridge, network-openvswitch, etc.) Those
will continue to use the general endpoint routine.
Partial-Bug: 1412919
Change-Id: Ia08983f6f8da8a96da22969cdb660b44f82780d6
- Set ['openstack']['network']['region'] to equal ['openstack']['region']
- Add test to override the endpoint region and confirm it is used
Change-Id: I68463f8cad7c424115ad75a39068c880ad3d3ef9
Addresses: blueprint uniform-region
all cops now pass except for the following
(which are silenced in .rubocop.yml )
* LineLength, MethodLength: not sure if we care about these
* WordArray: I prefer [] vs %w{} for readability.
Conflicts:
metadata.rb
recipes/common.rb
recipes/openvswitch.rb
spec/openvswitch_spec.rb
Change-Id: I92996b5db9f292e9ba93c7619ca727ffa92ddd71
Since in OpenStack Havana release the Quantum project was renamed to the
Neutron, for the cookbooks we also need do the same things to support
the Neutron. I do the %s/Quantum/Neutron/g in all the files under
cookbook-openstack-netwrok. It will effect other cookbooks:
openstack-compute, openstack-ops-database which should be covered in
others patches.
Implemented: blueprint neutron-support
Change-Id: I59f3f2d8dfad678f70b97d4cbc4e10dfa163e9b2
The python-quantumclient package may not include the correct
version of pyparsing in its dependencies, requiring us to
ensure that it is upgraded to the latest version prior to usage.
Needed to correct tests to pass openstack-common 0.4.0 changes.
Change-Id: Ia8507a5fe94322ff3106d12d161dcedf2ee19fdd
Ghanshyam Mann