Re: [rdo-list] [tripleo] Troubles deploying Libery with HA setup
by Pedro Sousa
Hi,
If you are trying to update the stack from 1 to 3 controllers, it will not
work, its not supported. You will have to delete the stack and start again
with 3 controllers. I also advise you to try mitaka.
Regards
Em 02/08/2016 17:00, "Luca 'remix_tj' Lorenzetto" <lorenzetto.luca(a)gmail.com>
escreveu:
Hello,
I'm deploying Liberty on a set of server using tripleo. I imported and
correctly introspected 6 nodes. First i did a setup with 1 controller
node and 3 computing nodes. No issues during this deploy, everything
went fine. On this deployment i used custom hostname formats (defined
via yaml environment file) and custom dns_domain (changed in
/etc/nova/nova.conf and /etc/neutron/dhcp_agent.ini and all
/usr/share/openstack-tripleo-heat-templates/*.yaml files that contains
localdomain)
Now I'm working to have a 3 controller setup with HA. I'm running this
command to deploy:
openstack overcloud deploy --templates -e
/usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml
-e ~/templates/network-environment.yaml -e
~/templates/puppet-ceph-external.yaml -e ~/hostname-nostri.yaml
--neutron-bridge-mappings datacentre:br-ex,storage-pub:br-stg-pub -e
/usr/share/openstack-tripleo-heat-templates/environments/puppet-pacemaker.yaml
--ntp-server timesrv1 --control-scale 3 --compute-scale 3
--ceph-storage-scale 0 --control-flavor controlhp --compute-flavor
computehp --neutron-network-type vxlan --neutron-tunnel-types vxlan
--verbose --debug --log-file overcloud_$(date +%T).log
I see that stack creation starts and correctly deploy os on the nodes.
Nodes are named according to ControllerHostnameFormat and
ComputeHostnameFormat that i specified into ~/hostname-nostri.yaml.
Everything goes well until HA configuration starts. I see this stack
creation failing:
overcloud-ControllerNodesPostDeployment-bbp3c47jgau2-ControllerLoadBalancerDeployment_Step1-sla6ce7n2arq
The error message of the deployment command is:
Stack failed with status: Resource CREATE failed:
resources.ControllerLoadBalancerDeployment_Step1:
resources.ControllerNodesPostDeployment.Error: resources[0]:
Deployment to server failed: deploy_status_code: Deployment exited
with non-zero status code: 6
Heat Stack create failed.
If i go in depth with heat deployment-show i see that all resources
report this deploy_stderr:
Error: Could not prefetch mysql_user provider 'mysql': Execution of
'/usr/bin/mysql -NBe SELECT CONCAT(User, '@',Host) AS User FROM
mysql.user' returned 1: ERROR 2002 (HY000): Can't connect to local
MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
Error: Could not prefetch mysql_database provider 'mysql': Execution
of '/usr/bin/mysql -NBe show databases' returned 1: ERROR 2002
(HY000): Can't connect to local MySQL server through socket
'/var/lib/mysql/mysql.sock' (2)\
Error: Command exceeded timeout
Error:
/Stage[main]/Pacemaker::Corosync/Exec[auth-successful-across-all-nodes]/returns:
change from notrun to 0 failed: Command exceeded timeout
Warning: /Stage[main]/Pacemaker::Corosync/Exec[Create Cluster
tripleo_cluster]: Skipping because of failed dependencies
Warning: /Stage[main]/Pacemaker::Corosync/Exec[Start Cluster
tripleo_cluster]: Skipping because of failed dependencies
Warning: /Stage[main]/Pacemaker::Corosync/Exec[wait-for-settle]:
Skipping because of failed dependencies
Warning: /Stage[main]/Pacemaker::Corosync/Notify[pacemaker settled]:
Skipping because of failed dependencies
Warning: /Stage[main]/Pacemaker::Stonith/Exec[Disable STONITH]:
Skipping because of failed dependencies",
I see nodes are stuck on puppet step
"auth-successful-across-all-nodes" (defined in
/etc/puppet/modules/pacemaker/manifests/corosync.pp)
/usr/bin/python2 /usr/sbin/pcs cluster auth opsctrl0 opsctrl1 opsctrl2
-u hacluster -p PASSWORD --force
I suppose that the problem is due to corosync service not yet started.
But as far as i can see corosync will never start because
/etc/corosync/corosync.conf file is missing.
in /etc/hosts opsctrl{0-2} are correctly defined and each host can
talk with the others.
I'm stuck and i don't know what to do. Anyone had similar issues? I'm
missing something that i have to enter in the configuration?
I'm using a in-house mirror of rdo-release made on April 20, and
custom images build from rhel image and this repository. A week ago i
tried with latest repository but had the same error (and also others,
that's why i returned to this older mirror that was working).
This is the list of packages installed from rdo-release repository:
crudini-0.7-1.el7.noarch
dib-utils-0.0.9-1.el7.noarch
dibbler-client-1.0.1-0.RC1.2.el7.x86_64
diskimage-builder-1.4.0-1.el7.noarch
erlang-asn1-R16B-03.16.el7.x86_64
erlang-compiler-R16B-03.16.el7.x86_64
erlang-crypto-R16B-03.16.el7.x86_64
erlang-erts-R16B-03.16.el7.x86_64
erlang-hipe-R16B-03.16.el7.x86_64
erlang-inets-R16B-03.16.el7.x86_64
erlang-kernel-R16B-03.16.el7.x86_64
erlang-mnesia-R16B-03.16.el7.x86_64
erlang-os_mon-R16B-03.16.el7.x86_64
erlang-otp_mibs-R16B-03.16.el7.x86_64
erlang-public_key-R16B-03.16.el7.x86_64
erlang-runtime_tools-R16B-03.16.el7.x86_64
erlang-sasl-R16B-03.16.el7.x86_64
erlang-sd_notify-0.1-1.el7.x86_64
erlang-snmp-R16B-03.16.el7.x86_64
erlang-ssl-R16B-03.16.el7.x86_64
erlang-stdlib-R16B-03.16.el7.x86_64
erlang-syntax_tools-R16B-03.16.el7.x86_64
erlang-tools-R16B-03.16.el7.x86_64
erlang-xmerl-R16B-03.16.el7.x86_64
hiera-1.3.4-1.el7.noarch
instack-0.0.8-1.el7.noarch
instack-undercloud-2.1.3-1.el7.noarch
jq-1.3-2.el7.x86_64
liberasurecode-1.1.1-1.el7.x86_64
libnetfilter_queue-1.0.2-2.el7.x86_64
memcached-1.4.25-1.el7.x86_64
1:openstack-ceilometer-alarm-5.0.2-1.el7.noarch
1:openstack-ceilometer-api-5.0.2-1.el7.noarch
1:openstack-ceilometer-central-5.0.2-1.el7.noarch
1:openstack-ceilometer-collector-5.0.2-1.el7.noarch
1:openstack-ceilometer-common-5.0.2-1.el7.noarch
1:openstack-ceilometer-notification-5.0.2-1.el7.noarch
1:openstack-ceilometer-polling-5.0.2-1.el7.noarch
1:openstack-glance-11.0.1-2.el7.noarch
1:openstack-heat-api-5.0.0-1.el7.noarch
1:openstack-heat-api-cfn-5.0.0-1.el7.noarch
1:openstack-heat-api-cloudwatch-5.0.0-1.el7.noarch
1:openstack-heat-common-5.0.0-1.el7.noarch
1:openstack-heat-engine-5.0.0-1.el7.noarch
openstack-heat-templates-0-0.1.20151019.el7.noarch
1:openstack-ironic-api-4.2.2-1.el7.noarch
1:openstack-ironic-common-4.2.2-1.el7.noarch
1:openstack-ironic-conductor-4.2.2-1.el7.noarch
openstack-ironic-inspector-2.2.2-1.el7.noarch
1:openstack-keystone-8.0.1-1.el7.noarch
1:openstack-neutron-7.0.3-1.el7.noarch
1:openstack-neutron-common-7.0.3-1.el7.noarch
1:openstack-neutron-ml2-7.0.3-1.el7.noarch
1:openstack-neutron-openvswitch-7.0.3-1.el7.noarch
1:openstack-nova-api-12.0.1-1.el7.noarch
1:openstack-nova-cert-12.0.1-1.el7.noarch
1:openstack-nova-common-12.0.1-1.el7.noarch
1:openstack-nova-compute-12.0.1-1.el7.noarch
1:openstack-nova-conductor-12.0.1-1.el7.noarch
1:openstack-nova-scheduler-12.0.1-1.el7.noarch
1:openstack-puppet-modules-7.0.1-1.el7.noarch
openstack-selinux-0.6.41-1.el7.noarch
openstack-swift-2.5.0-1.el7.noarch
openstack-swift-account-2.5.0-1.el7.noarch
openstack-swift-container-2.5.0-1.el7.noarch
openstack-swift-object-2.5.0-1.el7.noarch
openstack-swift-plugin-swift3-1.7-4.el7.noarch
openstack-swift-proxy-2.5.0-1.el7.noarch
openstack-tripleo-0.0.6-1.el7.noarch
openstack-tripleo-heat-templates-0.8.7-1.el7.noarch
openstack-tripleo-image-elements-0.9.7-1.el7.noarch
openstack-tripleo-puppet-elements-0.0.2-1.el7.noarch
openstack-utils-2015.2-1.el7.noarch
openvswitch-2.4.0-1.el7.x86_64
os-apply-config-0.1.32-3.el7.noarch
os-cloud-config-0.2.10-2.el7.noarch
os-collect-config-0.1.36-4.el7.noarch
os-net-config-0.1.5-3.el7.noarch
os-refresh-config-0.1.11-2.el7.noarch
puppet-3.6.2-3.el7.noarch
pyOpenSSL-0.15.1-1.el7.noarch
pyparsing-2.0.3-1.el7.noarch
pysendfile-2.0.0-5.el7.x86_64
pysnmp-4.2.5-2.el7.noarch
pystache-0.5.3-2.el7.noarch
python-alembic-0.8.3-3.el7.noarch
python-amqp-1.4.6-1.el7.noarch
python-anyjson-0.3.3-3.el7.noarch
python-automaton-0.7.0-1.el7.noarch
python-babel-1.3-6.el7.noarch
python-bson-3.0.3-1.el7.x86_64
python-cachetools-1.0.3-2.el7.noarch
1:python-ceilometer-5.0.2-1.el7.noarch
python-ceilometerclient-1.5.0-1.el7.noarch
python-cinderclient-1.4.0-1.el7.noarch
python-cliff-1.15.0-1.el7.noarch
python-cliff-tablib-1.1-3.el7.noarch
python-cmd2-0.6.8-3.el7.noarch
python-contextlib2-0.4.0-1.el7.noarch
python-croniter-0.3.4-2.el7.noarch
python-dogpile-cache-0.5.7-3.el7.noarch
python-dogpile-core-0.4.1-2.el7.noarch
python-ecdsa-0.11-3.el7.noarch
python-editor-0.4-4.el7.noarch
python-elasticsearch-1.4.0-2.el7.noarch
python-extras-0.0.3-2.el7.noarch
python-fixtures-1.4.0-2.el7.noarch
python-futures-3.0.3-1.el7.noarch
1:python-glance-11.0.1-2.el7.noarch
python-glance-store-0.9.1-1.el7.noarch
1:python-glanceclient-1.1.0-1.el7.noarch
python-heatclient-0.8.0-1.el7.noarch
python-httplib2-0.9.2-1.el7.noarch
python-idna-2.0-1.el7.noarch
python-ipaddress-1.0.7-4.el7.noarch
python-ironicclient-0.8.1-1.el7.noarch
python-jsonpatch-1.2-2.el7.noarch
python-jsonpath-rw-1.2.3-2.el7.noarch
python-jsonschema-2.3.0-1.el7.noarch
python-keyring-5.0-4.el7.noarch
1:python-keystone-8.0.1-1.el7.noarch
1:python-keystoneclient-1.7.2-1.el7.noarch
python-keystonemiddleware-2.3.1-1.el7.noarch
1:python-kombu-3.0.32-1.el7.noarch
python-ldappool-1.0-4.el7.noarch
python-linecache2-1.0.0-1.el7.noarch
python-logutils-0.3.3-3.el7.noarch
python-memcached-1.54-3.el7.noarch
python-migrate-0.10.0-1.el7.noarch
python-mimeparse-0.1.4-1.el7.noarch
python-monotonic-0.3-1.el7.noarch
python-ncclient-0.4.2-2.el7.noarch
python-netaddr-0.7.18-1.el7.noarch
python-netifaces-0.10.4-1.el7.x86_64
python-networkx-core-1.10-1.el7.noarch
1:python-neutron-7.0.3-1.el7.noarch
python-neutronclient-3.1.0-1.el7.noarch
python-nose-1.3.7-7.el7.noarch
1:python-nova-12.0.1-1.el7.noarch
1:python-novaclient-2.30.1-1.el7.noarch
python-oauthlib-0.7.2-5.20150520git514cad7.el7.noarch
python-openstackclient-1.7.2-1.el7.noarch
python-openvswitch-2.4.0-1.el7.noarch
python-oslo-cache-0.7.0-1.el7.noarch
python-oslo-concurrency-2.6.0-1.el7.noarch
python-oslo-db-2.6.0-3.el7.noarch
python-oslo-log-1.10.0-1.el7.noarch
python-oslo-messaging-2.5.0-1.el7.noarch
python-oslo-middleware-2.8.0-1.el7.noarch
python-oslo-policy-0.11.0-1.el7.noarch
python-oslo-rootwrap-2.3.0-1.el7.noarch
python-oslo-service-0.9.0-1.el7.noarch
python-oslo-versionedobjects-0.10.0-1.el7.noarch
python-oslo-vmware-1.21.0-1.el7.noarch
python-osprofiler-0.3.0-1.el7.noarch
python-paramiko-1.15.1-1.el7.noarch
python-paste-deploy-1.5.2-6.el7.noarch
python-pbr-1.8.1-2.el7.noarch
python-posix_ipc-0.9.8-1.el7.x86_64
python-prettytable-0.7.2-1.el7.noarch
python-proliantutils-2.1.7-1.el7.noarch
python-psutil-1.2.1-1.el7.x86_64
python-pycadf-1.1.0-1.el7.noarch
python-pyeclib-1.2.0-1.el7.x86_64
python-pyghmi-0.8.0-2.el7.noarch
python-pygments-2.0.2-4.el7.noarch
python-pymongo-3.0.3-1.el7.x86_64
python-pysaml2-3.0.2-1.el7.noarch
python-qpid-0.30-1.el7.noarch
python-qpid-common-0.30-1.el7.noarch
python-repoze-lru-0.4-3.el7.noarch
python-repoze-who-2.1-1.el7.noarch
python-requests-2.9.1-2.el7.noarch
python-retrying-1.2.3-4.el7.noarch
python-rfc3986-0.2.0-1.el7.noarch
python-routes-1.13-2.el7.noarch
python-saharaclient-0.11.1-1.el7.noarch
python-semantic_version-2.4.2-1.el7.noarch
python-simplegeneric-0.8-7.el7.noarch
python-simplejson-3.5.3-5.el7.x86_64
python-sqlalchemy-1.0.11-1.el7.x86_64
python-sqlparse-0.1.18-5.el7.noarch
python-stevedore-1.8.0-1.el7.noarch
python-swiftclient-2.6.0-1.el7.noarch
python-tablib-0.10.0-1.el7.noarch
python-taskflow-1.21.0-1.el7.noarch
python-tempita-0.5.1-8.el7.noarch
python-testtools-1.8.0-2.el7.noarch
python-tooz-1.24.0-1.el7.noarch
python-traceback2-1.4.0-2.el7.noarch
python-tripleoclient-0.0.11-3.el7.noarch
python-troveclient-1.3.0-1.el7.noarch
python-unicodecsv-0.14.1-1.el7.noarch
python-unittest2-1.0.1-1.el7.noarch
python-urllib3-1.13.1-3.el7.noarch
python-warlock-1.0.1-1.el7.noarch
python-webob-1.4.1-2.el7.noarch
python-websockify-0.6.0-2.el7.noarch
python-wrapt-1.10.5-3.el7.x86_64
python2-PyMySQL-0.6.7-2.el7.noarch
python2-appdirs-1.4.0-4.el7.noarch
python2-castellan-0.3.1-1.el7.noarch
python2-cffi-1.5.2-1.el7.x86_64
python2-cryptography-1.2.1-3.el7.x86_64
python2-debtcollector-0.8.0-1.el7.noarch
python2-eventlet-0.17.4-4.el7.noarch
python2-fasteners-0.14.1-4.el7.noarch
python2-funcsigs-0.4-2.el7.noarch
python2-futurist-0.5.0-1.el7.noarch
python2-greenlet-0.4.9-1.el7.x86_64
python2-ironic-inspector-client-1.2.0-2.el7.noarch
python2-iso8601-0.1.11-1.el7.noarch
python2-jsonpath-rw-ext-0.1.7-1.1.el7.noarch
python2-mock-1.3.0-1.el7.noarch
python2-os-brick-0.5.0-1.el7.noarch
python2-os-client-config-1.7.4-1.el7.noarch
2:python2-oslo-config-2.4.0-1.el7.noarch
python2-oslo-context-0.6.0-1.el7.noarch
python2-oslo-i18n-2.6.0-1.el7.noarch
python2-oslo-reports-0.5.0-1.el7.noarch
python2-oslo-serialization-1.9.0-1.el7.noarch
python2-oslo-utils-2.5.0-1.el7.noarch
python2-passlib-1.6.5-1.el7.noarch
python2-pecan-1.0.2-2.el7.noarch
python2-pyasn1-0.1.9-6.el7.1.noarch
python2-rsa-3.3-2.el7.noarch
python2-singledispatch-3.4.0.3-4.el7.noarch
python2-suds-0.7-0.1.94664ddd46a6.el7.noarch
python2-wsme-0.7.0-2.el7.noarch
rabbitmq-server-3.3.5-17.el7.noarch
ruby-augeas-0.5.0-1.el7.x86_64
ruby-shadow-1.4.1-23.el7.x86_64
rubygem-rgen-0.6.6-2.el7.noarch
tripleo-common-0.0.1-2.el7.noarch
Thank you,
Luca
--
"E' assurdo impiegare gli uomini di intelligenza eccellente per fare
calcoli che potrebbero essere affidati a chiunque se si usassero delle
macchine"
Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716)
"Internet è la più grande biblioteca del mondo.
Ma il problema è che i libri sono tutti sparsi sul pavimento"
John Allen Paulos, Matematico (1945-vivente)
Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , <
lorenzetto.luca(a)gmail.com>
_______________________________________________
rdo-list mailing list
rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
7 years, 8 months
Re: [rdo-list] Feedback around deploying an operating RDO/TripleO (was: Multiple tools for deploying and testing TripleO)
by David Moreau Simard
I think there's a lot of great and valuable feedback being exchanged
around the different means of deploying RDO, with or without TripleO
in that previous thread [1].
Let's spin that off into it's own thread so the community can discuss
this while keeping the other thread focused on continuous integration
efforts.
If you have any other thoughts around deploying and operating a cloud
built with RDO packages, please chime in here.
[1]: https://www.redhat.com/archives/rdo-list/2016-August/msg00002.html
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Tue, Aug 2, 2016 at 4:12 AM, Christopher Brown <cbrown2(a)ocf.co.uk> wrote:
> Hello RDOistas (I think that is the expression?),
>
> Another year, another OpenStack deployment tool. :)
>
> On Mon, 2016-08-01 at 18:59 +0100, Ignacio Bravo wrote:
>> If we are talking about tools, I would also want to add something
>> with regards to user interface of these tools. This is based on my
>> own experience:
>>
>> I started trying to deploy Openstack with Staypuft and The Foreman.
>> The UI of The Foreman was intuitive enough for the discovery and
>> provisioning of the servers. The OpenStack portion, not so much.
>
> This is exactly mine also. I think this works really well in very large
> enterprise environments where you need to split out services over more
> than three controllers. You do need good in-house puppet skills though
> so better for enterprise with a good sysadmin team.
>
>> Forward a couple of releases and we had a TripleO GUI (Tuskar, I
>> believe) that allowed you to graphically build your Openstack cloud.
>> That was a reasonable good GUI for Openstack.
>
> Well, I found it barely usable. It was only ever good as a graphical
> representiation of what the build was doing. Interacting with it was
> not great.
>
>> Following that, TripleO become a script based installer, that
>> required experience in Heat templates. I know I didn’t have it and
>> had to ask in the mailing list about how to present this or change
>> that. I got a couple of installs working with this setup.
>
> Works well now that I understand all the foibles and have invested time
> into understanding heat templates and puppet modules. Its good in that
> it forces you to learn about orchestration which is such an important
> end-goal of cloud environments.
>
>> In the last session in Austin, my goal was to obtain information on
>> how others were installing Openstack. I was pointed to Fuel as an
>> alternative. I tried it up, and it just worked. It had the
>> discovering capability from The Foreman, and the configuration
>> options from TripleO. I understand that is based in Ansible and
>> because of that, it is not fully CentOS ready for all the nodes (at
>> least not in version 9 that I tried). In any case, as a deployer and
>> installer, it is the most well rounded tool that I found.
>
> This is interesting to know. I've heard of Fuel of course but there are
> some politics involved - it still has the team:single-vendor tag but
> from what I see Mirantis are very keen for it to become the default
> OpenStack installer. I don't think being Ansible-based should be a
> problem - we are deploying OpenShift on OpenStack which uses Openshift-
> ansible - this recently moved to Ansible 2.1 without too much
> disruption.
>
>> I’d love to see RDO moving into that direction, and having an easy to
>> use, end user ready deployer tool.
>
> If its as good as you say its definitely worth evaluating. From our
> point of view, we want to be able to add services to the pacemaker
> cluster with some ease - for example Magnum and Sahara - and it looks
> like there are steps being taken with regards to composable roles and
> simplification of the pacemaker cluster to just core services.
>
> But if someone can explain that better I would appreciate it.
>
> Regards
>
>> IB
>>
>>
>> __
>> Ignacio Bravo
>> LTG Federal, Inc
>> www.ltgfederal.com
>>
>>
>> > On Aug 1, 2016, at 1:07 PM, David Moreau Simard <dms(a)redhat.com>
>> > wrote:
>> >
>> > The vast majority of RDO's CI relies on using upstream
>> > installation/deployment projects in order to test installation of
>> > RDO
>> > packages in different ways and configurations.
>> >
>> > Unless I'm mistaken, TripleO Quickstart was originally created as a
>> > mean to "easily" install TripleO in different topologies without
>> > requiring a massive amount of hardware.
>> > This project allows us to test TripleO in virtual deployments on
>> > just
>> > one server instead of, say, 6.
>> >
>> > There's also WeIRDO [1] which was left out of your list.
>> > WeIRDO is super simple and simply aims to run upstream gate jobs
>> > (such
>> > as puppet-openstack-integration [2][3] and packstack [4][5])
>> > outside
>> > of the gate.
>> > It'll install dependencies that are expected to be there (i.e,
>> > usually
>> > set up by the openstack-infra gate preparation jobs), set up the
>> > trunk
>> > repositories we're interested in testing and the rest is handled by
>> > the upstream project testing framework.
>> >
>> > The WeIRDO project is /very/ low maintenance and brings an
>> > exceptional
>> > amount of coverage and value.
>> > This coverage is important because RDO provides OpenStack packages
>> > or
>> > projects that are not necessarily used by TripleO and the reality
>> > is
>> > that not everyone deploying OpenStack on CentOS with RDO will be
>> > using
>> > TripleO.
>> >
>> > Anyway, sorry for sidetracking but back to the topic, thanks for
>> > opening the discussion.
>> >
>> > What honestly perplexes me is the situation of CI in RDO and OSP,
>> > especially around TripleO/Director, is the amount of work that is
>> > spent downstream.
>> > And by downstream, here, I mean anything that isn't in TripleO
>> > proper.
>> >
>> > I keep dreaming about how awesome upstream TripleO CI would be if
>> > all
>> > that effort was spent directly there instead -- and then that all
>> > work
>> > could bear fruit and trickle down downstream for free.
>> > Exactly like how we keep improving the testing coverage in
>> > puppet-openstack-integration, it's automatically pulled in RDO CI
>> > through WeIRDO for free.
>> > We make the upstream better and we benefit from it simultaneously:
>> > everyone wins.
>> >
>> > [1]: https://github.com/rdo-infra/weirdo
>> > [2]: https://github.com/rdo-infra/ansible-role-weirdo-puppet-openst
>> > ack
>> > [3]: https://github.com/openstack/puppet-openstack-integration#desc
>> > ription
>> > [4]: https://github.com/rdo-infra/ansible-role-weirdo-packstack
>> > [5]: https://github.com/openstack/packstack#packstack-integration-t
>> > ests
>> >
>> > David Moreau Simard
>> > Senior Software Engineer | Openstack RDO
>> >
>> > dmsimard = [irc, github, twitter]
>> >
>> > David Moreau Simard
>> > Senior Software Engineer | Openstack RDO
>> >
>> > dmsimard = [irc, github, twitter]
>> >
>> >
>> > On Mon, Aug 1, 2016 at 11:21 AM, Arie Bregman <abregman(a)redhat.com>
>> > wrote:
>> > > Hi,
>> > >
>> > > I would like to start a discussion on the overlap between tools
>> > > we
>> > > have for deploying and testing TripleO (RDO & RHOSP) in CI.
>> > >
>> > > Several months ago, we worked on one common framework for
>> > > deploying
>> > > and testing OpenStack (RDO & RHOSP) in CI. I think you can say it
>> > > didn't work out well, which eventually led each group to focus on
>> > > developing other existing/new tools.
>> > >
>> > > What we have right now for deploying and testing
>> > > --------------------------------------------------------
>> > > === Component CI, Gating ===
>> > > I'll start with the projects we created, I think that's only fair
>> > > :)
>> > >
>> > > * Ansible-OVB[1] - Provisioning Tripleo heat stack, using the OVB
>> > > project.
>> > >
>> > > * Ansible-RHOSP[2] - Product installation (RHOSP). Branch per
>> > > release.
>> > >
>> > > * Octario[3] - Testing using RPMs (pep8, unit, functional,
>> > > tempest,
>> > > csit) + Patching RPMs with submitted code.
>> > >
>> > > === Automation, QE ===
>> > > * InfraRed[4] - provision install and test. Pluggable and
>> > > modular,
>> > > allows you to create your own provisioner, installer and tester.
>> > >
>> > > As far as I know, the groups is working now on different
>> > > structure of
>> > > one main project and three sub projects (provision, install and
>> > > test).
>> > >
>> > > === RDO ===
>> > > I didn't use RDO tools, so I apologize if I got something wrong:
>> > >
>> > > * About ~25 micro independent Ansible roles[5]. You can either
>> > > choose
>> > > to use one of them or several together. They are used for
>> > > provisioning, installing and testing Tripleo.
>> > >
>> > > * Tripleo-quickstart[6] - uses the micro roles for deploying
>> > > tripleo
>> > > and test it.
>> > >
>> > > As I said, I didn't use the tools, so feel free to add more
>> > > information you think is relevant.
>> > >
>> > > === More? ===
>> > > I hope not. Let us know if are familiar with more tools.
>> > >
>> > > Conclusion
>> > > --------------
>> > > So as you can see, there are several projects that eventually
>> > > overlap
>> > > in many areas. Each group is basically using the same tasks
>> > > (provision
>> > > resources, build/import overcloud images, run tempest, collect
>> > > logs,
>> > > etc.)
>> > >
>> > > Personally, I think it's a waste of resources. For each task
>> > > there is
>> > > at least two people from different groups who work on exactly the
>> > > same
>> > > task. The most recent example I can give is OVB. As far as I
>> > > know,
>> > > both groups are working on implementing it in their set of tools
>> > > right
>> > > now.
>> > >
>> > > On the other hand, you can always claim: "we already tried to
>> > > work on
>> > > the same framework, we failed to do it successfully" - right, but
>> > > maybe with better ground rules we can manage it. We would
>> > > defiantly
>> > > benefit a lot from doing that.
>> > >
>> > > What's next?
>> > > ----------------
>> > > So first of all, I would like to hear from you if you think that
>> > > we
>> > > can collaborate once again or is it actually better to keep it as
>> > > it
>> > > is now.
>> > >
>> > > If you agree that collaboration here makes sense, maybe you have
>> > > ideas
>> > > on how we can do it better this time.
>> > >
>> > > I think that setting up a meeting to discuss the right
>> > > architecture
>> > > for the project(s) and decide on good review/gating process,
>> > > would be
>> > > a good start.
>> > >
>> > > Please let me know what do you think and keep in mind that this
>> > > is not
>> > > about which tool is better!. As you can see I didn't mention the
>> > > time
>> > > it takes for each tool to deploy and test, and also not the full
>> > > feature list it supports.
>> > > If possible, we should keep it about collaborating and not
>> > > choosing
>> > > the best tool. Our solution could be the combination of two or
>> > > more
>> > > tools eventually (tripleo-red, infra-quickstart? :D )
>> > >
>> > > "You may say I'm a dreamer, but I'm not the only one. I hope some
>> > > day
>> > > you'll join us and the infra will be as one" :)
>> > >
>> > > [1] https://github.com/redhat-openstack/ansible-ovb
>> > > [2] https://github.com/redhat-openstack/ansible-rhosp
>> > > [3] https://github.com/redhat-openstack/octario
>> > > [4] https://github.com/rhosqeauto/InfraRed
>> > > [5] https://github.com/redhat-openstack?utf8=%E2%9C%93&query=ansi
>> > > ble-role
>> > > [6] https://github.com/openstack/tripleo-quickstart
>> > >
>> > > _______________________________________________
>> > > rdo-list mailing list
>> > > rdo-list(a)redhat.com
>> > > https://www.redhat.com/mailman/listinfo/rdo-list
>> > >
>> > > To unsubscribe: rdo-list-unsubscribe(a)redhat.com
>> > _______________________________________________
>> > rdo-list mailing list
>> > rdo-list(a)redhat.com
>> > https://www.redhat.com/mailman/listinfo/rdo-list
>> >
>> > To unsubscribe: rdo-list-unsubscribe(a)redhat.com
>>
> --
> Regards,
>
> Christopher Brown
> OpenStack Engineer
> OCF plc
>
> Tel: +44 (0)114 257 2200
> Web: www.ocf.co.uk
> Blog: blog.ocf.co.uk
> Twitter: @ocfplc
>
> Please note, any emails relating to an OCF Support request must always
> be sent to support(a)ocf.co.uk for a ticket number to be generated or
> existing support ticket to be updated. Should this not be done then OCF
> cannot be held responsible for requests not dealt with in a timely
> manner.
>
> OCF plc is a company registered in England and Wales. Registered number
> 4132533, VAT number GB 780 6803 14. Registered office address: OCF plc,
> 5 Rotunda Business Centre, Thorncliffe Park, Chapeltown, Sheffield S35
> 2PG.
>
> This message is private and confidential. If you have received this
> message in error, please notify us immediately and remove it from your
> system.
>
> _______________________________________________
> rdo-list mailing list
> rdo-list(a)redhat.com
> https://www.redhat.com/mailman/listinfo/rdo-list
>
> To unsubscribe: rdo-list-unsubscribe(a)redhat.com
7 years, 8 months
[rdo-list] Upcoming OpenStack Meetups, week of Aug 1
by Rich Bowen
The following are the meetups I'm aware of in the coming week where
OpenStack and/or RDO enthusiasts are likely to be present. If you know
of others, please let me know, and/or add them to
http://rdoproject.org/events
If there's a meetup in your area, please consider attending. If you
attend, please consider taking a few photos, and possibly even writing
up a brief summary of what was covered.
--Rich
* Wednesday August 03 in Richardson, TX, US: Topic: Taming your
relational and non-relational databases with OpenStack Trove -
http://www.meetup.com/OpenStack-DFW/events/231162206/
* Wednesday August 03 in Singapore, SG: 8 Shenton Way, #10-00 AXA Tower
Red Hat Asia Pacific Pte Ltd, Singapore -
http://www.meetup.com/OpenStack-Singapore/events/232531940/
* Wednesday August 03 in Singapore, SG: Welcome, Stackers! -
http://www.meetup.com/Singapore-OPENSTACK-Evangelist-Meetup/events/232531...
* Wednesday August 03 in Singapore, SG: Welcome, Stackers! -
http://www.meetup.com/Singapore-OpenStack-User-Group-Meetup/events/232531...
* Wednesday August 03 in Tel Aviv-Yafo, IL: OpenStack Certified
Administrator Exam and Ansible Automation with Rackspace -
http://www.meetup.com/OpenStack-Israel/events/232840427/
* Thursday August 04 in Los Angeles, CA, US: RED HAT STORAGE DAY – Los
Angeles - http://www.meetup.com/Red-Hat-Los-Angeles/events/232762414/
* Thursday August 04 in Fort Lauderdale, FL, US: SFOUG Presentations -
http://www.meetup.com/South-Florida-OpenStack-Users-Group/events/232450735/
* Thursday August 04 in Wellington, NZ: Automating in the OpenStack
Cloud in Auckland -
http://www.meetup.com/New-Zealand-OpenStack-User-Group/events/232796455/
* Thursday August 04 in Wroclaw, PL: OpenStack Wrocław Meetup #2 -
http://www.meetup.com/Wroclaw-OpenStack-Meetup/events/232584503/
* Thursday August 04 in Austin, TX, US: Magnum: Openstack containers as
a service. - http://www.meetup.com/Docker-Austin/events/232067917/
* Saturday August 06 in Orlando, FL, US: OpenStack Build Day! -
http://www.meetup.com/Orlando-Central-Florida-OpenStack-Meetup/events/232...
* Sunday August 07 in Tambaram, IN: Swift Storage and its architecture -
http://www.meetup.com/CloudnLoud-Openstack-Cloud-RedHat-Opensource/events...
--
Rich Bowen - rbowen(a)redhat.com
RDO Community Liaison
http://rdoproject.org
@RDOCommunity
7 years, 8 months
[rdo-list] ask.openstack.org unanswered 'RDO' questions
by Rich Bowen
40 unanswered questions:
You are not authorized : identity:create_service
https://ask.openstack.org/en/question/94973/you-are-not-authorized-identi...
Tags: devstack#mitaka, mitaka-openstack, mitaka
RDO - is there any fedora package newer than puppet-4.2.1-3.fc24.noarch.rpm
https://ask.openstack.org/en/question/94969/rdo-is-there-any-fedora-packa...
Tags: rdo, puppet, install-openstack
OpenStack RDO mysqld 100% cpu
https://ask.openstack.org/en/question/94961/openstack-rdo-mysqld-100-cpu/
Tags: openstack, mysqld, cpu
Failed to set RDO repo on host-packstact-centOS-7
https://ask.openstack.org/en/question/94828/failed-to-set-rdo-repo-on-hos...
Tags: openstack-packstack, centos7, rdo
how to deploy haskell-distributed in RDO?
https://ask.openstack.org/en/question/94785/how-to-deploy-haskell-distrib...
Tags: rdo
How to set quota for domain and have it shared with all the
projects/tenants in domain
https://ask.openstack.org/en/question/94105/how-to-set-quota-for-domain-a...
Tags: domainquotadriver
rdo tripleO liberty undercloud install failing
https://ask.openstack.org/en/question/94023/rdo-tripleo-liberty-underclou...
Tags: rdo, rdo-manager, liberty, undercloud, instack
Add new compute node for TripleO deployment in virtual environment
https://ask.openstack.org/en/question/93703/add-new-compute-node-for-trip...
Tags: compute, tripleo, liberty, virtual, baremetal
Unable to start Ceilometer services
https://ask.openstack.org/en/question/93600/unable-to-start-ceilometer-se...
Tags: ceilometer, ceilometer-api
Adding hard drive space to RDO installation
https://ask.openstack.org/en/question/93412/adding-hard-drive-space-to-rd...
Tags: cinder, openstack, space, add
AWS Ec2 inst Eth port loses IP when attached to linux bridge in Openstack
https://ask.openstack.org/en/question/92271/aws-ec2-inst-eth-port-loses-i...
Tags: openstack, networking, aws
ceilometer: I've installed openstack mitaka. but swift stops working
when i configured the pipeline and ceilometer filter
https://ask.openstack.org/en/question/92035/ceilometer-ive-installed-open...
Tags: ceilometer, openstack-swift, mitaka
Fail on installing the controller on Cent OS 7
https://ask.openstack.org/en/question/92025/fail-on-installing-the-contro...
Tags: installation, centos7, controller
the error of service entity and API endpoints
https://ask.openstack.org/en/question/91702/the-error-of-service-entity-a...
Tags: service, entity, and, api, endpoints
Running delorean fails: Git won't fetch sources
https://ask.openstack.org/en/question/91600/running-delorean-fails-git-wo...
Tags: delorean, rdo
Liberty RDO: stack resource topology icons are pink
https://ask.openstack.org/en/question/91347/liberty-rdo-stack-resource-to...
Tags: stack, resource, topology, dashboard
Build of instance aborted: Block Device Mapping is Invalid.
https://ask.openstack.org/en/question/91205/build-of-instance-aborted-blo...
Tags: cinder, lvm, centos7
No handlers could be found for logger "oslo_config.cfg" while syncing
the glance database
https://ask.openstack.org/en/question/91169/no-handlers-could-be-found-fo...
Tags: liberty, glance, install-openstack
how to use chef auto manage openstack in RDO?
https://ask.openstack.org/en/question/90992/how-to-use-chef-auto-manage-o...
Tags: chef, rdo
Separate Cinder storage traffic from management
https://ask.openstack.org/en/question/90405/separate-cinder-storage-traff...
Tags: cinder, separate, nic, iscsi
Openstack installation fails using packstack, failure is in installation
of openstack-nova-compute. Error: Dependency Package[nova-compute] has
failures
https://ask.openstack.org/en/question/88993/openstack-installation-fails-...
Tags: novacompute, rdo, packstack, dependency, failure
CentOS OpenStack - compute node can't talk
https://ask.openstack.org/en/question/88989/centos-openstack-compute-node...
Tags: rdo
How to setup SWIFT_PROXY_NODE and SWIFT_STORAGE_NODEs separately on
RDO Liberty ?
https://ask.openstack.org/en/question/88897/how-to-setup-swift_proxy_node...
Tags: rdo, liberty, swift, ha
VM and container can't download anything from internet
https://ask.openstack.org/en/question/88338/vm-and-container-cant-downloa...
Tags: rdo, neutron, network, connectivity
Fedora22, Liberty, horizon VNC console and keymap=sv with ; and/
https://ask.openstack.org/en/question/87451/fedora22-liberty-horizon-vnc-...
Tags: keyboard, map, keymap, vncproxy, novnc
OpenStack-Docker driver failed
https://ask.openstack.org/en/question/87243/openstack-docker-driver-failed/
Tags: docker, openstack, liberty
Sahara SSHException: Error reading SSH protocol banner
https://ask.openstack.org/en/question/84710/sahara-sshexception-error-rea...
Tags: sahara, icehouse, ssh, vanila
Error Sahara create cluster: 'Error attach volume to instance
https://ask.openstack.org/en/question/84651/error-sahara-create-cluster-e...
Tags: sahara, attach-volume, vanila, icehouse
Creating Sahara cluster: Error attach volume to instance
https://ask.openstack.org/en/question/84650/creating-sahara-cluster-error...
Tags: sahara, attach-volume, hadoop, icehouse, vanilla
--
Rich Bowen - rbowen(a)redhat.com
RDO Community Liaison
http://rdoproject.org
@RDOCommunity
7 years, 8 months
