<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Harry,<br>
<br>
Thank you for the recap.<br>
I have just few questions/concerns about the following:<br>
<div class="" id="magicdomid58">
<ul class="list-bullet2">
<li><span
class="author-a-z77zsjz122zxz88zaz88zz65zl3ubz79zvz87z">review
role merging code: </span><span
class="author-a-z77zsjz122zxz88zaz88zz65zl3ubz79zvz87z
url"><a href="https://review.openstack.org/396694">https://review.openstack.org/396694</a></span></li>
<ul>
<li><span
class="author-a-z77zsjz122zxz88zaz88zz65zl3ubz79zvz87z
url">---> It missing the tripleo-backup role
(<a class="moz-txt-link-freetext" href="https://github.com/redhat-openstack/ansible-role-tripleo-backup">https://github.com/redhat-openstack/ansible-role-tripleo-backup</a>)<br>
</span></li>
</ul>
</ul>
</div>
<div class="" id="magicdomid59">
<ul class="list-bullet3">
<li><span class="author-a-z90zz90zcnuydz87zw4z66zz75zz85zaak">plan
is to run this merge script on Monday Nov. 21, </span><span
class="author-a-z77zsjz122zxz88zaz88zz65zl3ubz79zvz87z">and
push the history to the upstream repo</span></li>
<ul>
<li><span
class="author-a-z77zsjz122zxz88zaz88zz65zl3ubz79zvz87z">--->
does that means that it will keep the commit history and
the committer ids ? I think both a really important<br>
</span></li>
</ul>
</ul>
</div>
<div class="" id="magicdomid62">
<ul class="list-bullet2">
<li><span
class="author-a-38z72zz65zz88z0z81zz68zqz79z7inz86znz85z">Who
has permissions to merge in the new review.openstack.org
repo?</span></li>
<ul>
<li><span
class="author-a-38z72zz65zz88z0z81zz68zqz79z7inz86znz85z">--->
I'm afraid about this part, and it's mostly my cons
about one big repo. Currently I'm mostly the only one
who commit on the overcloud-upgrade role, which needs
sometimes some tricky fixes or immediate workarounds.
The current situation is ideal to me so I'm afraid to
have to loose this "cool" flexibility by waiting for 2
cores to vote on probably something that are really
"upgrade" specific and so hard-to-review
(s/hard/impossible/ ?). And it's probably the case for
all the special roles, which are really features
oriented. So did you guys plan to add more cores, and if
yes, who ? Afaik today, there is only 4 oooq-cores,
which is really weak for all the work that is done on
all of those roles...<br>
</span></li>
</ul>
</ul>
</div>
<br>
On 11/15/2016 07:46 PM, Harry Rybacki wrote:<br>
</div>
<blockquote
cite="mid:CAAfywTfa+KVk1jSnP1rbuh_HEsTCxMDuLU6gzTgiPEUxEJ3wfg@mail.gmail.com"
type="cite">
<pre wrap="">Greetings All,
Links to the RDO-Infra team's scrum etherpad[1] and video recording[2]
of the meeting are below.
Highlights:
- Move to combine tripleo-quickstart-extra roles into single repo
- Goal to perform merge early next week after Attila returns from PTO
- Opting for flat hierarchy (single role per repo breakdown)
- Need baremetal and ovb specific cores
- Moving virtual worikloads from bm to cloud on cico is delayed
- dmsimard is working on a infra/tooling roadmap for ocata[3]
- Liberty hits EOL on Thursday (17Nov2016)
[1] - <a class="moz-txt-link-freetext" href="https://review.rdoproject.org/etherpad/p/rdo-infra-scrum">https://review.rdoproject.org/etherpad/p/rdo-infra-scrum</a>
[2] - <a class="moz-txt-link-freetext" href="https://bluejeans.com/s/UftmN/">https://bluejeans.com/s/UftmN/</a>
[3] - <a class="moz-txt-link-freetext" href="https://review.rdoproject.org/etherpad/p/infra-ocata">https://review.rdoproject.org/etherpad/p/infra-ocata</a>
/R
Harry Rybacki
_______________________________________________
rdo-list mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a>
<a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/rdo-list">https://www.redhat.com/mailman/listinfo/rdo-list</a>
To unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:rdo-list-unsubscribe@redhat.com">rdo-list-unsubscribe@redhat.com</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>