| *** zbsarash1 has quit IRC | 01:06 | |
| *** dpanech has quit IRC | 01:44 | |
| *** yuxing has quit IRC | 02:03 | |
| *** sgw1 has quit IRC | 02:23 | |
| *** sgw1 has joined #starlingx | 02:54 | |
| *** sgw1 has quit IRC | 04:04 | |
| *** sgw1 has joined #starlingx | 04:06 | |
| *** yaawang has quit IRC | 04:10 | |
| *** yaawang has joined #starlingx | 04:11 | |
| *** sgw1 has quit IRC | 04:48 | |
| *** sgw1 has joined #starlingx | 04:52 | |
| *** yaawang has quit IRC | 05:16 | |
| *** yaawang has joined #starlingx | 05:16 | |
| *** psahoo has joined #starlingx | 05:55 | |
| *** psahoo has quit IRC | 06:22 | |
| *** yaawang has quit IRC | 06:26 | |
| *** yaawang has joined #starlingx | 06:27 | |
| *** psahoo has joined #starlingx | 06:40 | |
| *** born2bake has joined #starlingx | 07:13 | |
| *** bengates has joined #starlingx | 07:14 | |
| *** bengates has quit IRC | 07:14 | |
| *** bengates has joined #starlingx | 07:14 | |
| *** cfriesen has quit IRC | 07:44 | |
| *** bengates has quit IRC | 07:54 | |
| *** bengates has joined #starlingx | 07:54 | |
| *** yaawang has quit IRC | 08:24 | |
| *** yaawang has joined #starlingx | 08:31 | |
| *** psahoo has quit IRC | 09:14 | |
| *** psahoo has joined #starlingx | 09:30 | |
| *** yaawang has quit IRC | 10:24 | |
| *** yaawang has joined #starlingx | 10:25 | |
| *** ijolliffe has joined #starlingx | 12:29 | |
| *** mthebeau has quit IRC | 12:50 | |
| *** yuxing has joined #starlingx | 13:16 | |
| sgw1 | Morning all | 14:35 |
|---|---|---|
| admin0 | morning | 14:36 |
| *** ijolliffe has quit IRC | 14:38 | |
| *** cfriesen has joined #starlingx | 14:42 | |
| admin0 | quick question .. what does starlingX provides that is not easily attainable/configurable from other openstack projects ? | 14:49 |
| admin0 | there is openstack ansible, there is kolla ansible . redhat, mirantis .. what are the reasons to chose startlingx among others ? | 14:50 |
| bwensley | I would look here for your answer: https://www.starlingx.io/learn/ | 14:54 |
| admin0 | bwensley, found it .. many thanks | 14:56 |
| admin0 | the use cases mentions for example smart city/buildings .. for an operator/integrator like me, who wants to introudce this to customers, is there a use case or examples of how those are done | 14:57 |
| *** dpanech has joined #starlingx | 15:10 | |
| bwensley | Nothing that I am aware of. | 15:22 |
| *** mthebeau has joined #starlingx | 15:25 | |
| *** mthebeau has quit IRC | 15:27 | |
| sgw1 | dpanech: seems we might have to wait for a patch I just submitted to ansible-playbooks | 15:29 |
| *** zbsarash1 has joined #starlingx | 15:30 | |
| sgw1 | dpanech: sorry, I just saw an email from Ghada about the ansible-stuff, it was also in a commit message on a patch that merged | 15:30 |
| dpanech | sgw1: that's ok, I'm doing an initial build anyway... it takes a while for it to download the pre-requisites the first time | 15:31 |
| admin0 | is there a way to make the installer pxe supported ? | 15:32 |
| admin0 | so that someone does not need to be in the datacenter to setup/reinstall ? | 15:33 |
| sgw1 | admin0: your talking about the initial setup of controller-0? | 15:47 |
| sgw1 | your -> are you | 15:48 |
| sgw1 | slittle1: davlet, question about how the actual "release" build is created? I see that we have a version manifest in 2.0 and 3.0 like this: stx.2.0.1-default.xml or stx.3.0.0-default.xml | 15:51 |
| sgw1 | for 4.0 and layered build, what's the expected set of xml files supposed to look like? can we put them in a sub-directory in manifests? I need to test if repo can handle that maybe | 15:52 |
| sgw1 | or just have the *.xml file just prefixed with the release name like stx.4.0.0-flock.xml? | 15:53 |
| *** billzvonar has joined #starlingx | 16:06 | |
| *** bengates has quit IRC | 16:53 | |
| *** bengates has joined #starlingx | 16:54 | |
| sgw1 | bwensley: Can you take a look at https://review.opendev.org/741248 and poke the other cores, this is needed for the 4.0 build I was not aware until today since the cert-armada change merged instead of being blocked on this change. | 16:57 |
| *** bengates has quit IRC | 16:58 | |
| bwensley | Will do. | 16:59 |
| sgw1 | dpanech: Ok, I think everything should now be really in place for a 4.0 build. | 17:17 |
| *** psahoo has quit IRC | 17:19 | |
| dpanech | sgw1: compiler layer is built, building distro now. It's downloading stuff... I'll build the layers separately, then do one more combined build that should pick up your changes | 17:20 |
| sgw1 | Ok, is monolithic also going on the side? If so, it might need to be restarted to pick up the changes | 17:22 |
| *** mthebeau has joined #starlingx | 17:23 | |
| dpanech | sgw1: yes it's still going -- I'll restart it after | 17:29 |
| sgw1 | dpanech: why wait? If it does not reuse artifacts, it's a wasted build | 17:39 |
| dpanech | sgw1: ok restarted monolithic | 17:40 |
| sgw1 | dpanech: Great, could you send a follow up email to the failures explaining what you did, it just help so people not here understand what's going on. | 17:47 |
| * sgw1 off to swim for a bit | 17:48 | |
| *** dpanech has quit IRC | 20:03 | |
| *** mthebeau has quit IRC | 23:01 | |
| *** born2bake has quit IRC | 23:28 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!