[rdo-list] [Proposal] Improve clients maintenance on Fedora
by Haïkel
Hi,
If you're not aware, RDO is still maintaining OpenStack clients on Fedora.
As many developers, end-users of RDO are using Fedora, it is important
to provide at least
client-side utilities so that more people can use OpenStack.
I must admit, I'm doing a poor job as it's still semi-manual and we have to
deal with sync issues.
To improve that situation, I will be working on improving the tooling but also
came up with this proposal to distribute the load.
1. create an OpenStack SIG within Fedora, initial members will be current
RDO provenpackagers and volunteers
2. transfer ownership of all OpenStack packages to the SIG.
This will enable any SIG member to sync packages.
3. set up more reliable automation to do the sync (will still required
to be run by a human
to handle manual merges)
4. set up proper CI to test clients on a weekly basis.
All development will still happen in RDO gerrit, all discussions will
happen during RDO weekly
meeting.
I plan to submit this + improvements that will be suggested in this
thread to the next meeting,
so speak up :)
Regards,
H.
7 years, 1 month
[rdo-list] static delorean-deps repos
by Wesley Hayutin
Greetings,
Had a brief discussion on the release delivery meeting this morning with
Jon Schlueter where as the rel-del had a requirement for the CI to
constantly execute to retest any potential changes to the delorean-deps yum
repo. This is required because it informs the import process.
Ideally we don't have to constantly tax both our hardware and people
resources because we have have an unpinned repo that can change at any
moment.
A static delorean-deps repo married to a delorean repo would be more
efficient for everyone. How that is achieved is under discussion.
This email is only to serve as an entry point for a public discussion
around that issue.
Thanks all!
7 years, 1 month
[rdo-list] Connecting to TripleO horizon (under quickstart)
by James LaBarre
Trying to find how I should be connecting to Horizon as installed in a
Quickstart installation.
My connection would look like this:
*MyLaptop -> vpn -> large-remote-host *
on the large-remote-host I have the undercloud (directly accessible from
large-remote-host) along with controller0 and novacompute0 (forwarded to
large-remote-host through undercloud).
How should I be connecting to Horizon, since I have so many
layers/redirects in between. For that matter, is there a way to
determine if Horizon is working at all ("openstack service list" doesn't
show horizon as a service).
(undercloud) [stack@undercloud ~]$ openstack service list
+----------------------------------+------------------+-------------------------+
| ID | Name |
Type |
+----------------------------------+------------------+-------------------------+
| 1aa733bdce734d4780b5b5e4ae95b3ae | zaqar-websocket |
messaging-websocket |
| 40706a02e7cc48ffbe96463899ffc233 | keystone |
identity |
| 42ec6a4be14e4caebfd966fbb7f5887e | neutron |
network |
| 4cc628ee478549ada4689f0bc07c2c4c | ironic |
baremetal |
| 4e8429ec9b67491480f7d61b425a2c0c | heat-cfn |
cloudformation |
| 7258afcb547d43e0ad4c8d28e91f68a5 | glance |
image |
| 798a3c89a2f54ca483c302c363d827b1 | zaqar |
messaging |
| 93161b7459a746f6a9ed96aa4fd896bc | mistral |
workflowv2 |
| a2b11439cec94045a1c98834809d8cdf | ironic-inspector |
baremetal-introspection |
| e14d7534fb7d404bb34796dcb8e6ec33 | swift |
object-store |
| e388a17a1e424c35acb067c5e2065682 | nova |
compute |
| ec8d9da35b724d50a4f309141d30f331 | heat |
orchestration |
| f5f02530289b487c90d6c7ef6c1fd73a | placement |
placement |
+----------------------------------+------------------+-------------------------+
I suspect the quickstart script didn't configure everything (run as bash
quickstart.sh --playbook quickstart-extras.yml --bootstrap --no-clone -t
all -S overcloud-validate -R master 127.0.0.2)
7 years, 1 month
[rdo-list] [Meeting] RDO meeting (2017-09-27) Minutes
by Haïkel
==============================
#rdo: RDO meeting - 2017-09-27
==============================
Meeting started by number80 at 15:01:06 UTC. The full logs are
available at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2017_09_27/2017/rdo...
.
Meeting summary
---------------
* roll call (number80, 15:01:27)
* LINK: https://etherpad.openstack.org/p/RDO-Meeting (number80,
15:03:00)
* Can we have DLRN api endpoint for OSP in RDO infrastructure?
(number80, 15:05:54)
* OSP will start reporting data too dlrn_api via the dlrn hash it was
imported from ... soon (trown, 15:24:43)
* Mailman3 migration (number80, 15:26:36)
* ACTION: Duck ping upstream about LMTP. Request for help if you can
(number80, 15:37:39)
* LINK: https://github.com/mailman/mailman/issues/152 (Duck,
15:39:12)
* open floor (number80, 15:45:56)
* amoralej chairing next meeting (number80, 15:46:14)
* LINK:
https://review.rdoproject.org/etherpad/p/dependencies-management
(number80, 15:47:55)
* ACTION: * help on brainstorming deps management (number80,
15:48:33)
Meeting ended at 15:52:55 UTC.
Action items, by person
-----------------------
* Duck
* Duck ping upstream about LMTP. Request for help if you can
People present (lines said)
---------------------------
* number80 (66)
* Duck (43)
* dmsimard (38)
* trown (28)
* myoung (28)
* openstack (13)
* arxcruz (10)
* jpena (8)
* amoralej (5)
* rbowen (2)
* rdogerrit (2)
* jschlueter (2)
* jruzicka (2)
* PagliaccisCloud (1)
* jatanmalde|lunch (1)
* chandankumar (1)
* jatanmalde (0)
Generated by `MeetBot`_ 0.1.4
7 years, 1 month
[rdo-list] DLRN api endpoint for OSP 10|11|12
by Arx Cruz
Hello,
In our effort to enable DLRN in RDO, we also would like to enable DLRN api
endpoint it in OSP (10|11|12) promote jobs. To do so, we would like to
request this for the infra team responsible to that.
This is important so we can consolidate one single way to handle the
packages, both for Upstream jobs, RDO jobs and OSP.
Can someone please help us to enable it? What's the proper way to request
this?
Kind regards,
Arx Cruz
7 years, 1 month
[rdo-list] RDO-Infra Sprint meeting - Sep 25
by Arx Cruz
Hello,
Here’s the highlights from TripleO CI Squad meeting from September 25
As many of you are aware, we are changing the way the team work, and
instead of each member work on their own silo, we are now focused on work
together to solve one epic task that will involve all the members. In other
words, to work as a real team.
We are also adopting the Ruck and Rover methodologie, where every week one
person will be responsible for monitoring the TripleO and RDO CI and
reporting issues, releasing the rest of the team of this duty in order to
focus on improvements in our CI. You can read more about Ruck and Rover
here: https://en.wikipedia.org/wiki/Ruckman_(Australian_rules_football)
We are going to work on sprints of one week each one, however, for this
particular sprint, we are going to work on that for two weeks, since this
is the first one and we are experimenting how things will go on.
-
Roles
-
The Ruck and the Rover will be responsible for any CI problems, so if
you have anything related to CI, please contact them. The rest
of the team
will work on the sprint
-
Ruck
-
Wes Hayutin
-
Gael 9/26 and 9/27
-
Rover
-
John Trowbridge
-
Team
-
Arx Cruz
-
Ronelle Landy
-
Attila Darazs
-
Gabriele Cerami
-
Sagi Shnaidman
-
Gael Chamoulaud
-
Matt Young
-
Scrum
-
We are going to have daily “automatic” scrum, where each member of
the team will write on
https://etherpad.openstack.org/p/tripleo-ci-squad-scrum what they are
doing, what they are planning next, and any blocks. We will also have two
quickly meetings per week to discuss and review the tasks.
-
For this sprint
-
After review the proposed topics from the UA, the team voted to work
on utilizing the DLRN api across TripleO and RDO to report job status and
promotions. The reason was that this is a good exercise to the whole team
get knowledge about DLRN and also the perfect timing since we are between
releases, and this will be required for future tasks that we
have in queue.
-
The epic task with more information can be found here
https://trello.com/c/5FnfGByl/334-base-the-promotion-pipeline-of-upstream...
-
Tasks can be found in both the trelo card above, or in the TripleO Ci
Squad trello board using the filter by label “Sprint 1 (Sep 25 - Oct 10)”
or clicking in this link here
https://trello.com/b/U1ITy0cu/tripleo-ci-squad?menu=filter&filter=label:S...
If you have any questions, suggestions please let us know. Your feedback is
very important to us!
Kind regards,
Arx Cruz
7 years, 1 month
