Hello, It's time for our weekly PaaS SIG sync-up meeting
SAME TIME: 1700 UTC NEW TIME: Noon Eastern Standard Time NEW TIME: 11:00 am Central Standard Time
What??? UTC does not have daylight savings. So the time did not change. Most of North America has daylight savings, so the time shifted one hour earlier.
Time: 1700 UTC - Wedensdays Date: Today Wedensday, 16 November 2016 Where: IRC- Freenode - #centos-devel
Agenda: - OpenShift Current Status -- rpms -- Documentation -- Automated testing -- images / image building - Do we need to change our time? - Open Floor
On Wed, Nov 16, 2016 at 9:56 AM, Troy Dawson tdawson@redhat.com wrote:
Hello, It's time for our weekly PaaS SIG sync-up meeting
SAME TIME: 1700 UTC NEW TIME: Noon Eastern Standard Time NEW TIME: 11:00 am Central Standard Time
What??? UTC does not have daylight savings. So the time did not change. Most of North America has daylight savings, so the time shifted one hour earlier.
Time: 1700 UTC - Wedensdays Date: Today Wedensday, 16 November 2016 Where: IRC- Freenode - #centos-devel
Agenda:
- OpenShift Current Status
-- rpms
- We will be building ansible 2.2.0.0 from the OSE repository -- http://ftp.redhat.com/pub/redhat/linux/enterprise/7Server/en/RHOSE/SRPMS/ans... -- This builds the same as the one in EPEL but doesn't have build dependencies for packages not in RHEL, nor the tests that require those build dependencies. -- When the ConfigManagement SIG get's their ansible builds available, we will transition over to theirs.
- We will have ci build the origin 1.4.0 rc1 and openshift-ansible 3.4.0 rpm's in cbs
-- Documentation -- Automated testing -- images / image building
- Do we need to change our time?
Nope If you weren't able to make the meeting due to the time, please let us know.
- Open Floor
- Cockpit would like to build their package in the Paas SIG. Although this isn't the perfect fit, it does fit. -- There were no objections.
On 16/11/16 17:58, Troy Dawson wrote:
- We will have ci build the origin 1.4.0 rc1 and openshift-ansible
3.4.0 rpm's in cbs
how is this going to work ? tell me more... are we using a cbs bot/creds on ci.centos.org ?
My main interest here is to shoe-horn the atomic-openshift-installer into the process so we can both test the deployment from it, and the upgrade path from it.
-- Documentation -- Automated testing -- images / image building
- Do we need to change our time?
Nope If you weren't able to make the meeting due to the time, please let us know.
I havent been able to make the last few meetings due to being in hack sessions, face2face meetings or travelling. But otherwise this time works for me
Regards,
On Thu, Nov 17, 2016 at 5:30 AM, Karanbir Singh mail-lists@karan.org wrote:
On 16/11/16 17:58, Troy Dawson wrote:
- We will have ci build the origin 1.4.0 rc1 and openshift-ansible
3.4.0 rpm's in cbs
how is this going to work ? tell me more... are we using a cbs bot/creds on ci.centos.org ?
My main interest here is to shoe-horn the atomic-openshift-installer into the process so we can both test the deployment from it, and the upgrade path from it.
We are using the sig-paas credentials from the slave. So this is interesting since the current repo for the installer is hard coded. When we build from source we do build the installer as well and we will need to point to the one we built from source to have this work the way we want. Otherwise we would just install whatever is on build mirror.
I am open to other suggestions if you have them.
-- Documentation -- Automated testing -- images / image building
- Do we need to change our time?
Nope If you weren't able to make the meeting due to the time, please let us
know.
I havent been able to make the last few meetings due to being in hack sessions, face2face meetings or travelling. But otherwise this time works for me
Regards,
-- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 17/11/16 14:25, Ari LiVigni wrote:
So this is interesting since the current repo for the installer is hard coded. When we build from source we do build the installer as well and we will need to point to the one we built from source to have this work the way we want. Otherwise we would just install whatever is on build mirror.
agree. we might also need a new version string in there, origin-future ?
On Thu, Nov 17, 2016 at 9:37 AM, Karanbir Singh mail-lists@karan.org wrote:
On 17/11/16 14:25, Ari LiVigni wrote:
So this is interesting since the current repo for the installer is hard coded. When we build from source we do build the installer as well and we will need to point to the one we built from source to have this work the way we want. Otherwise we would just install whatever is on build mirror.
agree. we might also need a new version string in there, origin-future ?
Yes when I tried to run cbs it failed because origin doesn't belong in future. We are pretty close to having a really nice end to end solution here
-- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On Thu, Nov 17, 2016 at 8:52 AM, Ari LiVigni ari@redhat.com wrote:
On Thu, Nov 17, 2016 at 9:37 AM, Karanbir Singh mail-lists@karan.org wrote:
On 17/11/16 14:25, Ari LiVigni wrote:
So this is interesting since the current repo for the installer is hard coded. When we build from source we do build the installer as well and we will need to point to the one we built from source to have this work the way we want. Otherwise we would just install whatever is on build mirror.
agree. we might also need a new version string in there, origin-future ?
Yes when I tried to run cbs it failed because origin doesn't belong in future. We are pretty close to having a really nice end to end solution here
Added origin to the future tags. Sorry, I thought I'd already done that.
Troy
KB and Troy,
Just to summarize
Build from source Nightly: 1 - Build origin from source 2 - Build openshift-ansible from source (atomic-openshift-installer) 3 - Deploy cluster with bfs of above 4 - Run e2e basic tests on the cluster that was created 5 - On success cbs future-candidate
Committed code pulling from future-candidate every week?: 1 - Pull future-candidate for origin and openshift-ansible 2 - Deploy cluster with repos of above 3 - Run e2e conformance tests 4 - On success cbs future-testing
The things that are up in the air atm are around the installer. It seems you cannot override the repo that origin gets pulled from at run time. There is an env variable OO_INSTALL_PUDDLE_REPO that gets set I believe. When I have run this it seems to always pull in a yum repo when running atomic-openshift-installer at execution.
I am open to suggestions or maybe I am missing something. The build from source and cbs components work as desired atm.
Thanks,
On Thu, Nov 17, 2016 at 10:46 AM, Troy Dawson tdawson@redhat.com wrote:
On Thu, Nov 17, 2016 at 8:52 AM, Ari LiVigni ari@redhat.com wrote:
On Thu, Nov 17, 2016 at 9:37 AM, Karanbir Singh mail-lists@karan.org wrote:
On 17/11/16 14:25, Ari LiVigni wrote:
So this is interesting since the current repo for the installer is
hard
coded. When we build from source we do build the installer as well
and
we will need to point to the one we built from source to have this
work
the way we want. Otherwise we would just install whatever is on build mirror.
agree. we might also need a new version string in there, origin-future ?
Yes when I tried to run cbs it failed because origin doesn't belong in future. We are pretty close to having a really nice end to end solution here
Added origin to the future tags. Sorry, I thought I'd already done that.
Troy _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel