[Meeting] RDO meeting (2017-11-15) minutes
by Haïkel
==============================
#rdo: RDO meeting - 2017-11-15
==============================
Meeting started by dmsimard at 15:02:51 UTC. The full logs are
available at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2017_11_15/2017/rdo...
.
Meeting summary
---------------
* rollcall (dmsimard, 15:03:37)
* Queens Test day (hguemar, 15:04:54)
* LINK: https://www.rdoproject.org/testday/queens/milestone1/
(hguemar, 15:06:43)
* ACTION: hguemar sends reminder about test day on user/devel lists
(hguemar, 15:09:17)
* rdopkg: what to do with `rdopkg update-patches`? (hguemar, 15:09:46)
* `rdopkg patch -l --bump-only` is smarter and more robust alternative
to old `rdopkg update-patches` (which is in turn a rewrite on
ancient `update-patches.sh` script that started this whole patches
branch thing) (jruzicka, 15:10:14)
* users tell me it's convenient to have a `rdopkg patch`-like action
that is guaranteed to work on local patches branch and not overwrite
it (implicit -l/--local-patches) (jruzicka, 15:10:30)
* ACTION: jruzicka discuss rdopkg update-patches with jschlueter
(hguemar, 15:17:58)
* rdopkg .spec Release bumping (hguemar, 15:18:21)
* under review with some relevant comments:
https://softwarefactory-project.io/r/#/c/10200/ (jruzicka,
15:19:13)
* ACTION: everyone with mad .spec Release bumping skillz please review
this patch: https://softwarefactory-project.io/r/#/c/10200/
(jruzicka, 15:24:44)
* Looking for new project ideas which can done as a part of easyfix in
order to foster new contributors (hguemar, 15:25:37)
* ACTION: everyone help finding new ideas for easyfix (hguemar,
15:27:48)
* LINK:
https://www.rdoproject.org/use/bookmarks/01-tripleo-cheatsheet-deploying-...
(rbowen, 15:30:43)
* DLRN on TripleO CI usage of GitHub repos (hguemar, 15:35:04)
* ACTION: dmsimard to talk to Technical Committee about external
sources in TripleO (follow-up from Denver discussion) (dmsimard,
15:46:53)
* Upstream LTS releases discussion (hguemar, 15:50:21)
* LINK: https://etherpad.openstack.org/p/LTS-proposal (EmilienM,
15:50:32)
* LINK:
http://lists.openstack.org/pipermail/openstack-dev/2017-November/124308.html
(EmilienM, 15:53:50)
* jpena chairing next week (hguemar, 16:05:07)
Meeting ended at 16:05:34 UTC.
Action items, by person
-----------------------
* dmsimard
* dmsimard to talk to Technical Committee about external sources in
TripleO (follow-up from Denver discussion)
* hguemar
* hguemar sends reminder about test day on user/devel lists
* jruzicka
* jruzicka discuss rdopkg update-patches with jschlueter
* **UNASSIGNED**
* everyone with mad .spec Release bumping skillz please review this
patch: https://softwarefactory-project.io/r/#/c/10200/
* everyone help finding new ideas for easyfix
People present (lines said)
---------------------------
* hguemar (95)
* dmsimard (58)
* EmilienM (38)
* jruzicka (30)
* jpena (26)
* amoralej (19)
* chandankumar (17)
* openstack (12)
* PagliaccisCloud (9)
* rbowen (8)
* adarazs|ruck (4)
* jjoyce (3)
* ykarel (2)
* Duck (2)
* weshay (1)
* myoung (0)
Generated by `MeetBot`_ 0.1.4
8 years
Reminder: Test day tomorrow, Friday
by Rich Bowen
REMINDER: Queens milestone 1 test day tomorrow, Friday
Details here: http://rdoproject.org/testday/queens/milestone1/
We will be holding a RDO test day on November 16th and 17th, 2017.
This will be coordinated through the #rdo channel on Freenode, and
through this website and the rdo-list mailing list.
We'll be testing the first Queens milestone release. If you can do any
testing on your own ahead of time, that will help ensure that everyone
isn't encountering the same problems.
We will also be available for people that want to try the stable (Pike)
release.
--
Rich Bowen: Community Architect
rbowen(a)redhat.com
@rbowen // @RDOCommunity // @CentOSProject
1 859 351 9166
8 years
RDO registry outage
by David Moreau Simard
Hi,
We incurred a loss of data on the RDO registry today around 4PM UTC during
the SSL certificate renewal for the different domains and services used for
the registry.
Around 10PM UTC, everything should be back to normal.
Instead of re-building the lost images in-place, we expedited the upgrade
of our registry to OpenShift 3.7.
Our implementation of this brand new release contains, amongst other
things, a fix to prevent this issue from occurring again.
We built and pushed the following images to recover from what we had:
- master/tripleo-ci-testing: https://trunk.rdoproject.org/
centos7-master/df/24/df24d6e51a178263940fa929d52276f3697f75bd_3b7cc045
- master/current-tripleo-rdo: https://trunk.rdoproject.org/
centos7-master/3b/85/3b85715c6488a692fcdf4e4c6a589d77c60eb5a6_a3792c8d
- pike/tripleo-ci-testing: https://trunk.rdoproject.org/centos7-pike/16/ee/
16ee91b0fdf092037bd8cd788ffcd6476367ff08_940a986d
- pike/current-tripleo-rdo: https://trunk.rdoproject.org/centos7-pike/ca/08/
ca0834685d9bf226816e49b195251bd553fe5d9f_c74c332d
The last images builds and tags were pushed around 10PM UTC.
Note that we disabled Jenkins in order to prevent the periodic promotion
jobs from interfering or failing outright.
For this reason, if you see errors in your patches with 'NOT_REGISTERED',
feel free to do a recheck.
Thanks,
David Moreau Simard
Senior Software Engineer | OpenStack RDO
dmsimard = [irc, github, twitter]
8 years
Validation failure logs, OOO Quickstart
by James LaBarre
I keep trying to build tripleo-quickstart with different parameters, and
at the end of a 2+ hour process, it fails at validation. Problem is,
even with a "verbose" option in the command, I have absolutely no clue
on why the build failed. Just where does the process keep it's log
information?
With the verbose option, it bombs out at :
=================================
TASK [did the deployment pass or fail?]
****************************************
task path: /root/.quickstart/playbooks/quickstart-extras-overcloud.yml:41
Friday 10 November 2017 16:57:13 -0500 (0:00:00.071) 2:12:25.331
*******
fatal: [localhost]: FAILED! => {
"changed": false,
"failed": true,
"failed_when_result": true,
"invocation": {
"module_args": {
"var": "overcloud_deploy_result"
},
"module_name": "debug"
},
"overcloud_deploy_result": "failed"
}
=================================
I'd really like to figure out where it's failing, rather than having to
run yet another 2 or more hour run just to see it fail at the end (I had
tried caching the image files locally with the hopes I could cut the
build time down, but that hasn't cut off enough time).
Starting the build with:
export OOOtimestamp=`date +%Y%m%d_%H%M`
export GenConfig=minimal
export ReleaseName=pike
export ClusterNodes=config/nodes/3ctlr_1comp.yml
bash quickstart.sh --playbook quickstart-extras.yml --bootstrap
--no-clone --config config/general_config/${GenConfig}.yml -t all -S
overcloud-validate -R ${ReleaseName} -N $ClusterNodes -v 127.0.0.2 |&
tee ~/OOOlog_${OOOtimestamp}.txt
(I'm using the variables so I can have a consistent run script, should
probably make the timestamp log name run as part of the command)
8 years
Re: [rdo-users] rdo container registry url returns 404
by Alan Pevec
Hi Aneesh,
let's move discussion to the RDO users list so others can benefit and
there is also issue with TripleO docs which we need to clarify with
developers working on it.
On Wed, Nov 8, 2017 at 4:00 PM, Aneesh Puttur <aputtur(a)redhat.com> wrote:
> Hi Alan,
> I have a question on RDO registry for docker images. I was told by my
> colleague that you will be able to help, but if not, do you mind pointing me
> to the right person who could help me?
>
> I am trying tripleO Containers based Overcloud Deployment and as per their
> document
> (https://docs.openstack.org/tripleo-docs/latest/install/containers_deploym...),
> I am trying the following URL as a namespace to pull all container images.
>
> --namespace trunk.registry.rdoproject.org/master
>
> "openstack overcloud container image prepare \
>
> --namespace trunk.registry.rdoproject.org/master \
> --tag tripleo-ci-testing \
This is wrong in docs, testing tag should not be used outside CI jobs
since it can change any time also it is not confirmed it is working at
all!
> --push-destination 192.168.24.1:8787 \
> --output-images-file overcloud_containers.yaml
>
> "
>
> But this results in 404 error
>
> docker pull failed: Error: image
> master/centos-binary-aodh-api:tripleo-passed-ci not found
> retrying pulling image:
> trunk.registry.rdoproject.org/master/centos-binary-aodh-api
> docker pull failed: Error: image
> master/centos-binary-aodh-api:tripleo-passed-ci not found
> retrying pulling image:
> trunk.registry.rdoproject.org/master/centos-binary-aodh-api
> docker pull failed: Error: image
> master/centos-binary-aodh-api:tripleo-passed-ci not found
>
> Is this correct URL?
It is but there was an issue with tagging tripleo-passed-ci after
successful CI promotion, this is being worked on.
In the meantime, you can grab the hash from the last passed-ci RDO
trunk repository and use it as a tag:
$ python -c 'import urllib2;import
yaml;c=yaml.load(urllib2.urlopen("https://trunk.rdoproject.org/centos7-master/current-tripleo/commit.yaml"))["commits"][0];print
"%s_%s" % (c["commit_hash"],c["distro_hash"][0:8])'
3b85715c6488a692fcdf4e4c6a589d77c60eb5a6_a3792c8d
# a quick test that container image is there:
$ skopeo inspect
docker://trunk.registry.rdoproject.org/master/centos-binary-nova-api:3b85...
Cheers,
Alan
8 years, 1 month
Add baremetal to quickstart install
by James LaBarre
I'm wondering if it's possible to add a baremetal compute node to a
tripleo-quickstart setup after the system is installed (or, perhaps a
way to add the baremetal to a playbook). I expect one of the big
problems will be getting the controller & undercloud to communicate
outside it's virtual network.
I had also considered doing a completely manual install, making
virtualBMC VM nodes for undercloud & controller, although the network
communication still ends up being an issue.
8 years, 1 month
[Meeting] RDO meeting (2017-11-08) minutes
by YATIN KAREL
==============================
#rdo: RDO meeting - 2017-11-08
==============================
Meeting started by ykarel at 15:01:11 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2017_11_08/2017/rdo...
.
Meeting summary
---------------
* roll call (ykarel, 15:01:34)
* Queens Test day is on 16th, 17th November, website updated
https://www.rdoproject.org/testday/queens/milestone1/ (ykarel,
15:04:07)
* Fedora OpenStack SIG update (ykarel, 15:06:26)
* added some people in the SIG FAS group (number80, 15:06:59)
* will start transferring ownership to SIG soon (number80, 15:07:14)
* Upstream LTS releases discussion:
https://etherpad.openstack.org/p/SYD-forum-upstream-lts-releases
(ykarel, 15:10:12)
* LINK:
https://etherpad.openstack.org/p/SYD-forum-upstream-lts-releases
(jpena, 15:10:39)
* Open Discussion (ykarel, 15:20:08)
* Chair for next meeting (ykarel, 15:23:36)
* ACTION: number80 to chair next meeting (ykarel, 15:24:16)
* ACTION: Duck to bring meeting time discussion to the list
(number80, 15:30:13)
Meeting ended at 15:35:29 UTC.
Action items, by person
-----------------------
* Duck
* Duck to bring meeting time discussion to the list
* number80
* number80 to chair next meeting
People present (lines said)
---------------------------
* number80 (35)
* ykarel (33)
* Duck (13)
* jpena (8)
* amoralej (7)
* jruzicka (7)
* openstack (7)
* jschlueter (3)
* ssbarnea (1)
* aditya_r (1)
Generated by `MeetBot`_ 0.1.4
_______________________________________________
users mailing list
users(a)lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/users
To unsubscribe: users-unsubscribe(a)lists.rdoproject.org
8 years, 1 month
Maintenance on review.rdoproject.org tonight @ 23:30 UTC
by David Moreau Simard
Hi,
We'll be doing a maintenance on review.rdoproject.org tonight, tuesday
november 7th at 23:30 UTC ( 06:30PM EST ) in order to update Jenkins
components.
We'll put Jenkins in maintenance mode around 22:30 UTC in order to let the
ongoing builds finish before we start the maintenance.
Thanks,
David Moreau Simard
Senior Software Engineer | OpenStack RDO
dmsimard = [irc, github, twitter]
8 years, 1 month
