Commit Graph

10 Commits

Author SHA1 Message Date
Andreas Jaeger 47efe1f1e3 Retire repository
Fuel repositories are all retired in openstack namespace, retire
remaining fuel repos in x namespace since they are unused now.

This change removes all content from the repository and adds the usual
README file to point out that the repository is retired following the
process from
https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project

See also
http://lists.openstack.org/pipermail/openstack-discuss/2019-December/011675.html

A related change is: https://review.opendev.org/699752 .

Change-Id: I016c6c7263df9aefc9758d7f58168ec595894726
2019-12-18 20:09:39 +01:00
Igor Zinovik a371b6312b Provide a flag that mark existence of provider network
Puppet provider does not detect presence of provider network
'admin_floating_net' and tries to create it on each deployment run.
Introduce flag that will mark that network exist.

Change-Id: Idf02399bef4cff4d9dcfa0f3f68f5e70466f4a87
Closes-bug: #1626927
2016-11-10 14:18:37 +03:00
Igor Zinovik 94d6fe0d40 Fix package installation
Use default puppet modules that comes from fuel-library package.
Without them it is not possible to install unauthenticaed packages.

This change makes plugin compatible with Fuel 9.1

Change-Id: I0852983ec8d7912ea64b6f6bc88207ea817657f4
Closes-bug: #1633093
2016-10-14 15:40:38 +03:00
Igor Zinovik 42e87317d6 Introduce execution restriction on nsx-t-neutron-network-create task
Deployment task nsx-t-neutron-network create make two tenant networks
that are used for OSTF checks (test launch instances in internal network
and verify that VMs can successfulyy reach each other and external IP
addresses).

Root cause of the problem is that if we try to create networks twice
(run deployment task two times) it will fail with error that
"physical_network_type does not support being update". It is not
possible to run this task twice, to avoid such behaviour YAQL condition
prevents task from being run no more than one time. Task is executed
only when 'quantum' value (which determines that Neutron is enabled for
current environment) is changed, which should not happen during normal
operation (it is possible to switch this setting via fuel CLI, but not
through web UI).

Change-Id: Idd3000cdec0ef0c990c352d2cb7814fb4743d6f2
Closes-bug: #1626927
2016-09-26 17:15:33 +03:00
Artem Savinov fcaa0cc3e5 Setting up compute nodes to work with nsx-t
Added nsx-t components to compute node
Added create predefined network

Change-Id: I8647c220c4f8750b503568655d1be4a1774845d7
2016-09-09 13:13:32 +03:00
Artem Savinov 24cd70e987 Configure nova on compute-vmware role to support nsx-t
Change-Id: I17520b619c243b2faf9695992ca366525822ccb1
2016-09-06 11:19:23 +03:00
Artem Savinov 9728ea3bb4 Deploy controller node with nsx-t support
Change-Id: Iae2b2679b4f7bdbc1fe5b82aa2c0f2b46e032907
2016-09-01 12:21:53 +00:00
Artem Savinov 85be272e7d Add manifest to install custom repo on node with nsx packages
We cannot distribute nsx-t packages together with the plugin.
The user has to put packages in
/var/www/naillgun/plugins/nsx-t-1.0/deployment_scripts/puppet/modules/nsxt/files/packages
and we deploy custom repo with nsx-t packages on all openctack
controller/compute nodes.

Change-Id: I41dbb47bfa722061fc4b8b46ab8b94e6e3af8c94
2016-08-29 12:47:08 +00:00
Igor Zinovik c6eac64196 Implement plugin actions: install package, configure nsx.ini
Implement two deployment actions:
* python-vmware-nsx (contains Neutron NSX plugin) installation
* pass UI parameters into nsx.ini file

Plugin contains custom type `nsx_config' to configure settings in
nsx.ini file.

Plugin reuses network:neutron:core:nsx component due to a hardcoded
restriction in fuel UI. This makes impossible simultaneous usage of
NSX-T and NSXv plugins.

Change-Id: I963a9a8c1d5d8c27324bf01a6ae10be23075f413
2016-08-16 19:30:16 +03:00
Igor Zinovik 19755eb391 Add plugin stub 2016-07-25 17:50:26 +03:00