*** sdake has joined #openstack-operators | 00:00 | |
*** sdake_ has quit IRC | 00:00 | |
*** sdake has quit IRC | 00:13 | |
*** jamesdenton has joined #openstack-operators | 00:22 | |
*** jamesdenton has quit IRC | 00:40 | |
*** manheim has quit IRC | 01:10 | |
*** mriedem has quit IRC | 01:42 | |
*** sdake has joined #openstack-operators | 03:01 | |
*** sudipto has joined #openstack-operators | 03:05 | |
*** sudipto_ has joined #openstack-operators | 03:05 | |
*** ircuser-1 has joined #openstack-operators | 03:09 | |
*** sudipto has quit IRC | 03:12 | |
*** sudipto_ has quit IRC | 03:12 | |
*** bvandenh has quit IRC | 03:24 | |
*** VW_ has joined #openstack-operators | 03:30 | |
*** VW has quit IRC | 03:30 | |
*** sdake_ has joined #openstack-operators | 03:30 | |
*** VW_ has quit IRC | 03:31 | |
*** VW has joined #openstack-operators | 03:31 | |
*** sdake has quit IRC | 03:34 | |
*** VW has quit IRC | 03:57 | |
*** VW has joined #openstack-operators | 04:16 | |
*** saneax-_-|AFK is now known as saneax | 04:22 | |
*** sdake_ has quit IRC | 04:42 | |
*** sudipto_ has joined #openstack-operators | 04:57 | |
*** sudipto has joined #openstack-operators | 04:57 | |
*** fragatina has joined #openstack-operators | 05:39 | |
*** fragatina has quit IRC | 05:43 | |
*** fragatina has joined #openstack-operators | 05:44 | |
*** twi99y has joined #openstack-operators | 06:22 | |
*** VW has quit IRC | 06:34 | |
*** fragatina has quit IRC | 06:39 | |
*** fragatina has joined #openstack-operators | 07:01 | |
*** fragatina has quit IRC | 07:06 | |
*** Oku_OS-away is now known as Oku_OS | 07:08 | |
*** rcernin has joined #openstack-operators | 07:20 | |
*** pcaruana has joined #openstack-operators | 07:20 | |
*** rcernin has quit IRC | 07:23 | |
*** rcernin has joined #openstack-operators | 07:23 | |
*** jsheeren has joined #openstack-operators | 07:33 | |
*** sdake_ has joined #openstack-operators | 07:40 | |
*** karthikpr has quit IRC | 08:02 | |
*** Guest68960 has quit IRC | 08:14 | |
*** mgagne has joined #openstack-operators | 08:20 | |
*** mgagne is now known as Guest11443 | 08:20 | |
*** yprokule has joined #openstack-operators | 08:23 | |
*** sdake has joined #openstack-operators | 08:26 | |
*** manheim has joined #openstack-operators | 08:26 | |
*** sdake_ has quit IRC | 08:27 | |
*** dbecker has joined #openstack-operators | 08:49 | |
*** sdake has quit IRC | 08:59 | |
*** jsheeren has quit IRC | 09:10 | |
*** rmart04 has joined #openstack-operators | 09:17 | |
*** zioproto has joined #openstack-operators | 09:17 | |
*** yprokule_ has joined #openstack-operators | 09:20 | |
*** yprokule has quit IRC | 09:20 | |
*** yprokule_ is now known as yprokule | 09:20 | |
*** manheim has quit IRC | 09:33 | |
*** electrofelix has joined #openstack-operators | 09:40 | |
*** racedo has joined #openstack-operators | 09:43 | |
*** yprokule_ has joined #openstack-operators | 09:47 | |
*** yprokule has quit IRC | 09:48 | |
*** yprokule_ is now known as yprokule | 09:48 | |
*** cartik has joined #openstack-operators | 09:49 | |
*** derekh has joined #openstack-operators | 10:04 | |
*** manheim_ has joined #openstack-operators | 10:42 | |
*** manheim_ has quit IRC | 10:44 | |
*** fyxim_ has quit IRC | 10:52 | |
*** bvandenh has joined #openstack-operators | 10:58 | |
*** jsheeren has joined #openstack-operators | 10:59 | |
*** arnewiebalck has quit IRC | 11:00 | |
*** arnewiebalck has joined #openstack-operators | 11:05 | |
*** manheim_ has joined #openstack-operators | 11:10 | |
*** bvandenh has quit IRC | 11:36 | |
*** sudipto_ has quit IRC | 11:58 | |
*** sudipto has quit IRC | 11:58 | |
zioproto | Hello ops | 12:02 |
---|---|---|
zioproto | I am testing a migration Mitaka to Newton | 12:02 |
zioproto | when I do the db migrations in nova | 12:02 |
zioproto | I get | 12:02 |
zioproto | error: There are still 2 unmigrated records in the compute_nodes table. Migration cannot continue until all records have been migrated. | 12:03 |
zioproto | from the release notes I dont see anything about this compute_nodes table | 12:03 |
*** raalee has joined #openstack-operators | 12:05 | |
*** cartik has quit IRC | 12:05 | |
*** saneax is now known as saneax-_-|AFK | 12:27 | |
*** bsilverman_7 has quit IRC | 12:36 | |
*** bsilverman_ has joined #openstack-operators | 12:36 | |
*** sudipto has joined #openstack-operators | 12:50 | |
*** sudipto_ has joined #openstack-operators | 12:50 | |
*** jsheeren has quit IRC | 13:00 | |
*** jamesdenton has joined #openstack-operators | 13:01 | |
*** jamesdenton has quit IRC | 13:04 | |
*** rmart04 has quit IRC | 13:04 | |
*** rmart04 has joined #openstack-operators | 13:04 | |
*** liverpooler has joined #openstack-operators | 13:18 | |
*** dminer has joined #openstack-operators | 13:34 | |
*** manheim_ has quit IRC | 13:35 | |
mrhillsman | hey zioproto | 13:39 |
mrhillsman | i have not tried any mitaka to newton upgrades | 13:39 |
mrhillsman | but maybe this will help - https://ask.openstack.org/en/question/101518/urgent-newton-nova-db-sync-not-migrating-compute_nodes-table/ | 13:39 |
mrhillsman | they suggest reading a few things before trying to run any further commands | 13:40 |
mrhillsman | possibly related to cells being required newton+ | 13:40 |
zioproto | yes I am already following that path | 13:41 |
zioproto | looks like there is a lot in stable/mitaka that was never tagged for release | 13:41 |
zioproto | I am asking on #openstack-nova to make a latest tag for stable/mitaka branch before going EOL | 13:42 |
mrhillsman | ah ok | 13:42 |
yankcrime | drop table compute_nodes ? ;) | 13:43 |
zioproto | OH MY GOD | 13:48 |
zioproto | can anyone really confirm | 13:48 |
zioproto | that to run newton | 13:48 |
zioproto | I have to create yet another DB | 13:49 |
zioproto | called cell0 ? | 13:49 |
yankcrime | haha | 13:49 |
zioproto | is this really true ? | 13:49 |
yankcrime | we're a long ways of newton, i can't offer any insight unfortunately | 13:49 |
yankcrime | 🎻 | 13:49 |
*** manheim_ has joined #openstack-operators | 13:50 | |
mrhillsman | zioproto i cannot confirm you have to create another db | 13:54 |
mrhillsman | but i know you have to have cells | 13:54 |
mrhillsman | unfortunately i like yankcrime have not upgraded | 13:54 |
*** VW has joined #openstack-operators | 13:54 | |
*** tongli has joined #openstack-operators | 13:54 | |
mrhillsman | at least not outside of openstack-ansible deployment tool | 13:54 |
*** chlong has joined #openstack-operators | 13:59 | |
mrhillsman | #startmeeting osops | 14:00 |
openstack | Meeting started Mon Feb 27 14:00:02 2017 UTC and is due to finish in 60 minutes. The chair is mrhillsman. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:00 |
*** VW has quit IRC | 14:00 | |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:00 |
openstack | The meeting name has been set to 'osops' | 14:00 |
mrhillsman | #topic Roll Call | 14:00 |
yankcrime | o/ | 14:00 |
*** VW has joined #openstack-operators | 14:00 | |
mrhillsman | morning everyone, osops meeting for those who are available :) | 14:00 |
mrhillsman | agenda is here #link https://etherpad.openstack.org/p/osops-meeting | 14:01 |
mrhillsman | anyone else here besides myself and yankcrime | 14:02 |
mrhillsman | for the meeting that is :) | 14:02 |
robputt | afternoon all | 14:03 |
robputt | :-) | 14:03 |
yankcrime | hi robputt ! | 14:03 |
robputt | hey yankcrime, :-) | 14:03 |
mrhillsman | hey robputt | 14:04 |
*** chlong has quit IRC | 14:04 | |
cemason | i'm here as well :) | 14:04 |
mrhillsman | cemason welcome! | 14:04 |
mrhillsman | #topic State of the Repos | 14:04 |
mrhillsman | so as you can see on the agenda | 14:04 |
mrhillsman | the repos can use some love i think | 14:05 |
mrhillsman | but overall standardization | 14:05 |
*** VW has quit IRC | 14:05 | |
mrhillsman | unfortunately none of the folks from osic who have been working on this are in the meeting | 14:05 |
*** erhudy has joined #openstack-operators | 14:05 | |
mrhillsman | but here is some idea | 14:06 |
mrhillsman | https://github.com/osic/ops-generic | 14:06 |
*** VW has joined #openstack-operators | 14:06 | |
mrhillsman | something like, version the tool works with | 14:07 |
mrhillsman | known issues | 14:07 |
mdorman | o/ sorry for late | 14:08 |
robputt | having all the tools in one repo kinda breaks alot of stuff | 14:08 |
robputt | for example, you can't do a tagged version release of a given tool | 14:08 |
yankcrime | are we talking about defining a new taxonomy and doing away with the existing one? | 14:08 |
mrhillsman | nothing definitive | 14:08 |
*** cdelatte has joined #openstack-operators | 14:08 | |
mrhillsman | definitely doing something with the README | 14:08 |
*** manheim_ has quit IRC | 14:09 | |
mrhillsman | but that means each tool would have to be in a folder | 14:09 |
mrhillsman | if the current taxonomy works with some slight changes great | 14:09 |
mrhillsman | robputt agreed, i think that repo is just an example of structure for a repo | 14:10 |
yankcrime | i like the idea of 'contrib' but agreed wrt the proliferation of tools and versioning | 14:10 |
mrhillsman | we can keep all the ones we have | 14:10 |
mrhillsman | i like versioning as well | 14:10 |
robputt | I have to be honest, I dislike the structure | 14:11 |
mrhillsman | any recommendations on how | 14:11 |
robputt | there are a number of problems with it, such as, you are unable to use ansible in it's intended form loading modules via ansible-galaxy | 14:11 |
robputt | and if you want one tool you end up having this whole bloated repo | 14:11 |
robputt | my gut instinct tells me each tool should be its own repo | 14:12 |
mrhillsman | robputt do you mind taking action to recommend new structure | 14:12 |
robputt | with a tagged version release which is compatible with each openstack release, but I also appreciate that means we end up managing alot of repos | 14:12 |
*** mriedem has joined #openstack-operators | 14:12 | |
robputt | its hard to say mrhillsman, we are in danger of having lots of little repos | 14:13 |
yankcrime | i think it might put people off contributing simple scripts as well | 14:13 |
robputt | I can suggest a structure, but I think it would be unpopular as it would add additional management overhead | 14:13 |
robputt | yep, it's getting the balance right, its a complex one | 14:13 |
yankcrime | really i think you'd want a couple of people to volunteer to curate something like robputt's suggesting | 14:13 |
* yankcrime nods | 14:13 | |
robputt | ohhh for sure you'd need to have people actively act as owners of the repos | 14:14 |
robputt | we'd kind of have a "product owner" kind of head for each | 14:14 |
mrhillsman | with them being little someone could "product own" more than one yes? | 14:14 |
robputt | yeah of course | 14:14 |
mrhillsman | and with a standard would that make it easier to do so? | 14:15 |
robputt | there is a bit of me which says leave it as it is, and get the master branch to a point when it works for all scripts against the latest release | 14:15 |
robputt | and tag that as a "Works with Newton" release | 14:15 |
yankcrime | that sounds like a pragmatic way forward | 14:15 |
mrhillsman | +1 | 14:15 |
robputt | but it means we need to get all scripts in the repo in a known working state for a given openstack release | 14:16 |
mrhillsman | we can work on that in osic | 14:16 |
*** manheim_ has joined #openstack-operators | 14:16 | |
mrhillsman | so all agreed on that? | 14:16 |
robputt | we can then backport it to previous versions in a branch for each Openstack version | 14:16 |
robputt | yep I would agree | 14:16 |
robputt | I think the overhead of having a repo for each script is too much | 14:17 |
robputt | but versioned releases some how for the repos are pretty damn important I think | 14:17 |
mrhillsman | cool | 14:17 |
mrhillsman | we can discuss further definitely | 14:17 |
mrhillsman | i think getting it to works with x is a good first | 14:17 |
*** fyxim_ has joined #openstack-operators | 14:17 | |
*** jsheeren has joined #openstack-operators | 14:17 | |
* yankcrime nods | 14:18 | |
mrhillsman | cool, moving on | 14:18 |
*** fyxim_ is now known as fyxim | 14:18 | |
mrhillsman | #agreed get all tools to works with X status | 14:18 |
mdorman | +1 | 14:18 |
mrhillsman | #topic Wiki Cleanup | 14:18 |
mrhillsman | i want to discuss this with uc as it relates to the purpose of osops beyond the repos | 14:19 |
mrhillsman | and i think after such a discussion we can clean some of the stuff up on the wiki | 14:19 |
mrhillsman | just seems like stuff is everywhere | 14:20 |
yankcrime | what's the general UC steer on this stuff? | 14:20 |
yankcrime | or is that what you want to prompt? | 14:20 |
mrhillsman | that is what i want to prompt | 14:20 |
yankcrime | righto | 14:20 |
mrhillsman | i have an idea but could be totally off | 14:21 |
mrhillsman | wondering if anyone here has reviewed it and has any thoughts | 14:21 |
mrhillsman | or even tried to use it hehe | 14:21 |
*** sdake has joined #openstack-operators | 14:21 | |
robputt | no real thoughts | 14:21 |
mrhillsman | looks to need some tlc in general | 14:22 |
robputt | It would be nice to flesh it out with some product catalogue kind of style thing | 14:22 |
mrhillsman | hmmm...interesting | 14:22 |
robputt | for a new visitor "A repo of curated tools and scripts." doesn't really mean much when he is looking for some specific script | 14:22 |
mrhillsman | noting that | 14:22 |
mrhillsman | agreed | 14:22 |
yankcrime | yeah, good idea | 14:22 |
robputt | if we could list all of our scripts, which repo they live in, a status for the last few openstack releases of known compatability and maybe a roadmap for additions / improvements | 14:23 |
mrhillsman | and actually, that could help with not having to have complex repo setup | 14:23 |
mrhillsman | could standardize around the 'product catalogue'? | 14:24 |
mrhillsman | good stuff robputt | 14:24 |
mrhillsman | ok, anything else here? | 14:25 |
nishpatwa007 | robputt I would like to add | 14:25 |
nishpatwa007 | So https://github.com/osic/ops-generic is a more structured implementation of the some of the functionalities of ops tools contrib with reusable common libraries | 14:26 |
*** asettle has joined #openstack-operators | 14:26 | |
robputt | I see... | 14:27 |
mrhillsman | i'm going to go on to the next topic everyone unless we need to spend more time here | 14:27 |
nishpatwa007 | in that way its easier to add more scripts | 14:27 |
robputt | that makes me think of something else for either the wiki / github repos actually... | 14:27 |
robputt | each script could do with usage instructions / sample configs | 14:28 |
mdorman | or at least it’s supposed to be. in theory things from the contrib repo are supposed to be “promoted” up to the generic repo. but in practice i don’t think taht is happening much | 14:28 |
nishpatwa007 | Yes each tool has a readme for the usage and the requirements | 14:28 |
nishpatwa007 | so each directory is an autonomous entity | 14:28 |
robputt | yep, we need to add that because at the moment stuff like orphaned floating ip tool has no requirements.txt or a readme | 14:29 |
robputt | so for a new comer it maybe be a bit of a struggle to work out how to use it | 14:29 |
robputt | anyway I agree next topic, we are rabbit holing around what standards a tool needs to be included in generic rather than contrib | 14:29 |
mrhillsman | ok cool | 14:29 |
mrhillsman | we can discuss further of course later | 14:30 |
nishpatwa007 | cool | 14:30 |
mrhillsman | #topic Feedback Loop | 14:30 |
mrhillsman | #link https://github.com/openstack/openstack-user-stories | 14:30 |
mrhillsman | so we have these user stories | 14:30 |
mrhillsman | we definitely cannot "force" work i would say but more so influence it | 14:31 |
mrhillsman | the product team however would like operators to review the user stories | 14:31 |
*** sdake has quit IRC | 14:31 | |
mrhillsman | and from a technical/operator/end-user/etc standpoint ensure they make sense | 14:31 |
mrhillsman | these would basically bubble up to the UC who then advocate for the work | 14:32 |
mrhillsman | having operators review the user-story i believe the idea is it adds more value | 14:32 |
mdorman | +1 we should be helping review that stuff, and this is a place where we can influence new features on the front-end | 14:33 |
mrhillsman | yep | 14:33 |
mrhillsman | i will send an email to the ML at large | 14:33 |
mrhillsman | but wanted to get any feedback from you fine folks | 14:33 |
mrhillsman | #action mrhillsman email Ops ML regarding PWG user story reviews | 14:34 |
robputt | no real opinion on this, user stories should come from all of the places in my opinion | 14:34 |
robputt | :-) | 14:34 |
mrhillsman | agreed | 14:34 |
yankcrime | ops are users too! ;) | 14:34 |
mrhillsman | lol, yes, yes we are | 14:34 |
mrhillsman | ok cool, on to the next one | 14:35 |
mrhillsman | #topic Documentation | 14:35 |
mrhillsman | so, i think some folks have a misunderstanding around this | 14:35 |
mrhillsman | or maybe it has not been clear | 14:36 |
*** sdake has joined #openstack-operators | 14:36 | |
mrhillsman | ops folks are not asking to be taxed with doing the actual docs work | 14:36 |
mrhillsman | but rather review and feedback, filing bugs, etc | 14:36 |
robputt | I personally think the ops based documentation for Openstack could be improved across the board. | 14:36 |
mrhillsman | asettle am i wrong? | 14:37 |
asettle | Hey! | 14:37 |
robputt | there are lots of small bits that need tweaking to make stuff work as expected for new / inexperienced operators | 14:37 |
mrhillsman | docs folks are in agreement robputt afaik | 14:37 |
asettle | So, it's a 50/50, you're not wrong ;) but operators *do* have specialty knowledge that devs and tech writers just do not have. | 14:37 |
asettle | We do request/expect those gaps are often filled. | 14:37 |
asettle | Whether that be by bug reporting (letting us konw a change, an error, etc) or actually patching it up yourself. | 14:37 |
robputt | I am happy to submit patches | 14:37 |
asettle | robputt: that's the spirit ;) | 14:38 |
mrhillsman | +1 | 14:38 |
mrhillsman | same here | 14:38 |
robputt | but I have no clue about how the docs repos / workflow works | 14:38 |
asettle | If I can help, I will. I'm Alex o/ for those who haven't met me. | 14:38 |
asettle | I'm the docs PTL | 14:38 |
robputt | is it largely the same as any other OS project? | 14:38 |
asettle | robputt: exactly the same as dev. If you need help with it though, let me help you work it through | 14:38 |
asettle | No changes robputt :) | 14:38 |
mrhillsman | it is the same as any other ^ | 14:38 |
robputt | cool :-) | 14:38 |
asettle | https://github.com/openstack/openstack-manuals | 14:38 |
asettle | We like to ensure there's minimal difference. | 14:38 |
robputt | well in this case I have some changes for the Newton Debian 8 manual which I picked up the other day when deploying some stuff | 14:38 |
robputt | :-) | 14:38 |
mrhillsman | hehe | 14:39 |
asettle | robputt: the install guide? | 14:39 |
robputt | yep | 14:39 |
asettle | So, we just lost our Debian guy. So, please, patch away by all means. | 14:39 |
mrhillsman | there's some issues around debian i read | 14:39 |
asettle | Debian is no longer, in summary. | 14:39 |
mrhillsman | the packaging guy is gone or something | 14:39 |
asettle | We had one guy who was helping the team to package and manage the guides is gone. | 14:39 |
robputt | damn | 14:39 |
mrhillsman | yeah, hopefully it will get worked out | 14:39 |
asettle | The docs team already managers 3 distributions (well, 5) so keeping on debconf and debian was a hard slog. | 14:39 |
mrhillsman | there is a long thread about it | 14:40 |
asettle | So, we've had to drop it until another package manager comes our way. | 14:40 |
robputt | I can't promise packages, I hate packaging Python stuff inside of anything over the PyPi, but the docs I can submit updates for sure | 14:40 |
asettle | robputt: love your stuff :) it's not up in Ocata :( But Newton would love some attention if you have the time. | 14:40 |
asettle | I'm actually in the process of looking at the ops-guide we have up and will be owrking with our team leads to improve it and the admin guide | 14:40 |
asettle | https://docs.openstack.org/ops-guide/operations.html | 14:40 |
asettle | https://docs.openstack.org/admin-guide/ | 14:41 |
asettle | If anyone's interested in helping out these guys with me, please let me know :) | 14:41 |
mrhillsman | awesome, i'm going to go to the next topic because of timing | 14:42 |
asettle | Please do :) | 14:42 |
mrhillsman | thanks asettle ;) | 14:42 |
robputt | np, asettle i'll poke you later about docs stuff I have a few more queries | 14:42 |
mrhillsman | going to skip over ancillary tooling if no one objects | 14:42 |
asettle | robputt: jump on over to our chan if you have any questions :) #openstack-doc | 14:42 |
mrhillsman | and osic like environments | 14:43 |
robputt | well | 14:43 |
mrhillsman | #topic Underutilized Projects | 14:43 |
robputt | hang on | 14:43 |
mrhillsman | ok, going back | 14:43 |
mrhillsman | to which one? | 14:43 |
robputt | lets chat about osic like envs quickly | 14:43 |
robputt | :P | 14:43 |
mrhillsman | #topic OSIC-like Environments | 14:44 |
robputt | so I currently have "RobCloud" my personal Openstack playground | 14:44 |
*** jamesdenton has joined #openstack-operators | 14:44 | |
robputt | which massively sucks but I try stuff out in there which I want in a vanilla openstack deployment | 14:44 |
robputt | So, what opportunity is there for us getting access to OSIC like envs for testing out stuff | 14:45 |
robputt | in particular emerging Openstack projects? | 14:45 |
mrhillsman | anyone can request resources from osic | 14:45 |
mrhillsman | and for emerging projects even the more | 14:45 |
robputt | ok... but what about if we want to have control plane access? | 14:45 |
robputt | or are we expected to build a cloud ontop of the cloud for testing? | 14:45 |
mrhillsman | you get baremetal nodes | 14:46 |
robputt | ohhh ok cool :-) | 14:46 |
mrhillsman | and can do what your heart desires with tnem :) | 14:46 |
robputt | tbh its probably the same overhead as what I have now then for trying stuff out if you get bare metal | 14:46 |
mrhillsman | beyond that though, there are other options as well and i was hoping to discuss | 14:46 |
robputt | so these bare metal nodes, are they Ironic driven? | 14:47 |
mrhillsman | so you want openstack already live | 14:47 |
mrhillsman | they are ironic driven more than likely by now or definitely will be | 14:47 |
robputt | ok | 14:47 |
robputt | :-) | 14:47 |
mrhillsman | there is work to move all of the nodes under ironic | 14:47 |
mrhillsman | some are, some are not unfortunately | 14:47 |
robputt | let me take this offline mrhillsman | 14:47 |
mrhillsman | ok | 14:47 |
mrhillsman | there is also cloud native foundation and few other such osic-like environments | 14:48 |
robputt | but I would like to make use of OSIC for my Openstack adventures rather than my current setup as its a bit crummy ;-) | 14:48 |
mrhillsman | i was wondering if anyone knows of any, has any, is planning on having any, etc | 14:48 |
mrhillsman | i have a contact at AT&T who mentioned having something like osic there | 14:49 |
mrhillsman | but not sure what that means | 14:49 |
mrhillsman | so i will go on to the next | 14:49 |
mrhillsman | time running out hehe | 14:49 |
mrhillsman | #topic Underutilized Projects | 14:49 |
robputt | Yep, we need to get in here :-) | 14:49 |
robputt | big time | 14:49 |
mrhillsman | #link https://etherpad.openstack.org/p/ops-adopt-a-project-pike | 14:50 |
mrhillsman | so beyond the general issue of projects not having enough feedback and new ones needing more than those that have been around | 14:50 |
robputt | its not so much feedback | 14:50 |
mrhillsman | we started an effort in osic to help those that folks want to use | 14:50 |
mrhillsman | but just need that little extra push | 14:50 |
robputt | I would like us to get very early involvement so we can shape a product around operational acceptance from day one. | 14:51 |
mrhillsman | and i think the thought is good across the board | 14:51 |
mrhillsman | how can we get that to work | 14:51 |
mrhillsman | i assume we need test environments | 14:51 |
mrhillsman | tying into the osic-like topic | 14:52 |
mrhillsman | though they do not have to be large | 14:52 |
mrhillsman | but devstack would not be sufficient | 14:52 |
mrhillsman | from an operational standpoint | 14:52 |
klindgren | So we tried ironic. But honestly the "friction" between the ironic team and the nova team and the pace of getting something out there that was not crazy pants - was untenable. | 14:52 |
robputt | It doesn't need to be a large deployment, but silly stuff like | 14:52 |
robputt | "how does it scale" | 14:52 |
robputt | is often not even covered in new projects at all | 14:53 |
mrhillsman | klindgren i'd like to hear more | 14:54 |
klindgren | Something as simple as configuring a raid array for r10 or r5 or r1 & 5. The answer was "use seperate pools for each raid array. | 14:54 |
klindgren | Which means that I need to have 3 different config/pools of hardware for 1 piece of hardware | 14:54 |
klindgren | for requests to be pulled from. Ironic was build some placement api thing, for NOVa , but that took like 2 cycles - not even sure where it is in ocata | 14:55 |
mrhillsman | would like to hear more offline klindgren as it could be an issue going forward in general | 14:56 |
klindgren | Its also super easy to get an ironic node stuck | 14:56 |
mrhillsman | and probably something that needs to pushed up for discussion | 14:56 |
klindgren | reboot it while deploying an image to it - it will bascially never come back | 14:56 |
mrhillsman | so we have not so new projects and very new projects | 14:56 |
klindgren | must go to the db to clear the state, and remove the vm from nova | 14:56 |
yankcrime | early ops engagement for new and emerging projects would be a great idea imo | 14:57 |
robputt | we have a whole load of ugly around our ironic deployment :-( | 14:57 |
mrhillsman | i'd like to hear more about how that looks like | 14:57 |
robputt | well, just for example | 14:57 |
robputt | if we look at Picasso | 14:57 |
mrhillsman | new and emerging | 14:57 |
robputt | which is an uber new project | 14:58 |
robputt | and a pretty important one in my opinion, but maybe thats just my love for FaaS | 14:58 |
mrhillsman | #link https://wiki.openstack.org/wiki/Picasso | 14:58 |
robputt | it currently for me isn't really heading in the direction of operational acceptance in my opinion... | 14:58 |
klindgren | Some of the variables are one-sizes fits all (like the stty number to use for serial console on serial over lan) - but all hardware is snowflakes. So I actually have 2 peices of hardware that need different stty numbers. No way to handle that in ironic. | 14:58 |
robputt | For example, it is not configurable like a standard Openstack service, it doesn't use Oslo libs for stuff like DB / Messaging | 14:59 |
mrhillsman | i'm going to have to kill our meeting at 9 but feel free to keep going | 14:59 |
mrhillsman | i will capture things for next meeting | 14:59 |
robputt | it doesn't have a pluggable backend for using with multiple function runners etc... | 14:59 |
robputt | to me, as an operator I expect things to use the standard libs | 14:59 |
robputt | and to behave in an Openstacky kind of way | 14:59 |
mrhillsman | and we have to have buy-in from those projects no doubt | 14:59 |
robputt | once you have configured 1 OS project you should be able to configure them all | 14:59 |
yankcrime | so really our engagement should be at the blueprint stage | 15:00 |
robputt | yes totally | 15:00 |
mrhillsman | #endmeeting | 15:00 |
robputt | if we see a super mega early code commit using some nonsense with PyMySQL | 15:00 |
openstack | Meeting ended Mon Feb 27 15:00:20 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:00 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/osops/2017/osops.2017-02-27-14.00.html | 15:00 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/osops/2017/osops.2017-02-27-14.00.txt | 15:00 |
openstack | Log: http://eavesdrop.openstack.org/meetings/osops/2017/osops.2017-02-27-14.00.log.html | 15:00 |
yankcrime | or there should be something in the template that defines some semblance of production / operational acceptance, even if it's just anticipatory | 15:00 |
robputt | and not using Oslo.DB we should totally scream about it | 15:00 |
robputt | after all, ops don't want to be tied to one DB technology etc... | 15:00 |
yankcrime | yeah | 15:00 |
mrhillsman | +1 | 15:00 |
robputt | also other stuff, like for example | 15:01 |
*** trikky_one has joined #openstack-operators | 15:01 | |
robputt | Picasso is driven buy the iron.io guys, but it has no pluggable backend, which means I can't use it with Fission, or Kubernetes etc... | 15:01 |
*** jsheeren has quit IRC | 15:01 | |
*** raalee has quit IRC | 15:01 | |
robputt | We need to push the no vendor tie in thing on all Openstack projects | 15:01 |
mrhillsman | or i think in general they will die or be very limited in adoption | 15:02 |
robputt | for me keeping a keen eye on these early stage projects would be really beneficial for their growth and integration into the ecosystem | 15:02 |
yankcrime | their success absolutely depends on it tbh | 15:02 |
mrhillsman | yankcrime you brought up an interesting thing there | 15:02 |
mrhillsman | pardon my ignorance | 15:02 |
mrhillsman | but the guide for starting a project | 15:03 |
robputt | yep | 15:03 |
mrhillsman | it does not take into consideration operational/production acceptance criteria? | 15:03 |
yankcrime | if they're polarising operators by poor technology choices early on then it'll definitely stymie adoption | 15:03 |
robputt | yep for sure | 15:03 |
robputt | there is one reason why I don't run Picasso today as our internal Function as a Service API | 15:04 |
robputt | and thats lack of pluggable backend | 15:04 |
robputt | Iron.IO doesn't suit our usecase at all | 15:04 |
robputt | I would throw our internal FaaS out tommorow if Picasso had a pluggable backend and I could write a Fission driver for it | 15:04 |
robputt | ohhh and make it play nice with our ancient internal keystone :-D | 15:05 |
mrhillsman | i just want to thank everyone for participating | 15:05 |
mrhillsman | i had too much stuff on the agenda i see lol | 15:05 |
yankcrime | i've got to run to another meeting, this seems like a good start to the reboot though - cheers all! | 15:06 |
mrhillsman | agreed | 15:06 |
robputt | see you next time | 15:06 |
mrhillsman | have a great one | 15:06 |
robputt | mrhillsman: get another etherpad up | 15:06 |
mrhillsman | i'll send out summary | 15:06 |
robputt | so we can start throwing stuff in there for next time | 15:06 |
robputt | :-) | 15:06 |
mrhillsman | will do :) | 15:06 |
*** belmoreira has joined #openstack-operators | 15:09 | |
*** sdake_ has joined #openstack-operators | 15:20 | |
*** _ducttape_ has joined #openstack-operators | 15:21 | |
*** mriedem1 has joined #openstack-operators | 15:22 | |
*** mriedem has quit IRC | 15:23 | |
*** sdake has quit IRC | 15:23 | |
*** chlong has joined #openstack-operators | 15:25 | |
*** chlong_ has joined #openstack-operators | 15:27 | |
*** chlong_ has quit IRC | 15:28 | |
*** twi99y has quit IRC | 15:30 | |
*** twi99y has joined #openstack-operators | 15:30 | |
*** TxGirlGeek has joined #openstack-operators | 15:31 | |
*** TxGirlGeek has quit IRC | 15:32 | |
*** TxGirlGeek has joined #openstack-operators | 15:34 | |
*** mriedem1 is now known as mriedem | 15:37 | |
*** liverpooler has quit IRC | 15:43 | |
*** manheim_ has quit IRC | 15:46 | |
*** liverpooler has joined #openstack-operators | 15:48 | |
*** liverpooler has quit IRC | 15:49 | |
*** liverpooler has joined #openstack-operators | 15:49 | |
*** manheim_ has joined #openstack-operators | 15:52 | |
*** sdake_ is now known as sdake | 16:01 | |
*** Oku_OS is now known as Oku_OS-away | 16:02 | |
*** khappone has quit IRC | 16:07 | |
*** khappone has joined #openstack-operators | 16:10 | |
shewless | Hello. If I create a subnet and enable dhcp but don't specify a nameserver my instances have an IP in /etc/resolv.conf that is on the same subnet. Is this the behaviour of "local dnsmasque" | 16:13 |
*** rcernin has quit IRC | 16:15 | |
*** belmoreira has quit IRC | 16:17 | |
*** trikky_one has quit IRC | 16:18 | |
*** raalee has joined #openstack-operators | 16:18 | |
*** saybeano has joined #openstack-operators | 16:19 | |
*** manheim_ has quit IRC | 16:25 | |
*** manheim_ has joined #openstack-operators | 16:32 | |
*** mriedem has quit IRC | 16:44 | |
*** mriedem has joined #openstack-operators | 16:46 | |
*** gfhellma has joined #openstack-operators | 16:50 | |
*** twi99y_ has joined #openstack-operators | 17:03 | |
*** rmart04 has quit IRC | 17:03 | |
*** manheim_ has quit IRC | 17:04 | |
*** twi99y has quit IRC | 17:04 | |
*** yprokule has quit IRC | 17:12 | |
*** karthikpr has joined #openstack-operators | 17:13 | |
*** twi99y_ has quit IRC | 17:14 | |
*** twi99y has joined #openstack-operators | 17:15 | |
*** sudipto_ has quit IRC | 17:15 | |
*** sudipto has quit IRC | 17:15 | |
*** twi99y_ has joined #openstack-operators | 17:16 | |
*** david-lyle has joined #openstack-operators | 17:17 | |
*** twi99y has quit IRC | 17:19 | |
*** Apoorva has joined #openstack-operators | 17:20 | |
*** Apoorva has quit IRC | 17:20 | |
*** david-lyle has quit IRC | 17:21 | |
*** dminer has quit IRC | 17:21 | |
*** Apoorva has joined #openstack-operators | 17:23 | |
*** twi99y_ has quit IRC | 17:23 | |
*** twi99y has joined #openstack-operators | 17:23 | |
*** zioproto has quit IRC | 17:33 | |
*** karthikpr has quit IRC | 17:38 | |
*** manheim_ has joined #openstack-operators | 17:43 | |
*** marst has joined #openstack-operators | 17:43 | |
*** david-lyle has joined #openstack-operators | 17:44 | |
*** david-lyle has quit IRC | 17:45 | |
*** david-lyle has joined #openstack-operators | 17:46 | |
*** derekh has quit IRC | 17:47 | |
klindgren | I tought dhcp overwrote /etc/resolv.conf? | 17:48 |
*** fragatina has joined #openstack-operators | 17:50 | |
*** slaweq_ has quit IRC | 17:51 | |
*** slaweq_ has joined #openstack-operators | 17:53 | |
*** chlong has quit IRC | 17:55 | |
*** fragatina has quit IRC | 17:58 | |
*** david-lyle has quit IRC | 17:58 | |
*** fragatina has joined #openstack-operators | 17:58 | |
*** david-lyle has joined #openstack-operators | 18:01 | |
*** emagana has joined #openstack-operators | 18:09 | |
*** chlong has joined #openstack-operators | 18:10 | |
*** manheim_ has quit IRC | 18:12 | |
*** armax has joined #openstack-operators | 18:28 | |
*** sudipto_ has joined #openstack-operators | 18:40 | |
*** sudipto has joined #openstack-operators | 18:40 | |
*** _ducttape_ has quit IRC | 18:43 | |
*** ducttape_ has joined #openstack-operators | 18:44 | |
*** ducttape_ has quit IRC | 18:45 | |
*** ducttape_ has joined #openstack-operators | 18:45 | |
*** shamail has joined #openstack-operators | 18:45 | |
mrhillsman | it does/supposed to | 18:56 |
mrhillsman | but if you do not set a nameserver it uses 127.0.0.1 | 18:56 |
mrhillsman | at least that is what i read | 18:57 |
*** shamail has quit IRC | 18:58 | |
*** dminer has joined #openstack-operators | 18:58 | |
*** shamail has joined #openstack-operators | 19:06 | |
*** sudipto_ has quit IRC | 19:17 | |
*** sudipto has quit IRC | 19:17 | |
*** electrofelix has quit IRC | 19:25 | |
*** alop has joined #openstack-operators | 19:26 | |
*** sudipto_ has joined #openstack-operators | 19:27 | |
*** sudipto has joined #openstack-operators | 19:27 | |
*** pcaruana has quit IRC | 19:29 | |
*** sudipto_ has quit IRC | 19:32 | |
*** sudipto has quit IRC | 19:32 | |
*** manheim_ has joined #openstack-operators | 19:32 | |
*** sdake has quit IRC | 19:36 | |
*** gfhellma has quit IRC | 19:36 | |
*** manheim_ has quit IRC | 19:37 | |
*** sudipto has joined #openstack-operators | 19:39 | |
*** sudipto_ has joined #openstack-operators | 19:39 | |
*** Rockyg has joined #openstack-operators | 19:45 | |
*** sudipto has quit IRC | 19:46 | |
*** sudipto_ has quit IRC | 19:46 | |
*** shamail has quit IRC | 20:00 | |
shewless | I'm finding that my openstack will setup a "local nameserver" by default. I added my real dns to the dns forwarder endtry in the dhcp_agent.ini and things are working as I expect! | 20:07 |
shewless | Another question. How easy is it to modify the region name on an existing setup? select * from region; shows the "id" as the actual region name.. which makes me think I'd have to change all my endpoints and maybe more? | 20:08 |
shewless | or would I just need to update the endpoints? | 20:08 |
*** dminer has quit IRC | 20:16 | |
*** ducttape_ has quit IRC | 20:22 | |
*** emagana has quit IRC | 20:22 | |
*** gfhellma has joined #openstack-operators | 20:23 | |
*** _ducttape_ has joined #openstack-operators | 20:25 | |
*** dbecker has quit IRC | 20:27 | |
*** emagana has joined #openstack-operators | 20:28 | |
*** dminer has joined #openstack-operators | 20:30 | |
*** emagana has quit IRC | 20:36 | |
*** emagana has joined #openstack-operators | 20:38 | |
*** emagana has quit IRC | 20:43 | |
*** liverpooler has quit IRC | 20:50 | |
*** rcernin has joined #openstack-operators | 20:52 | |
*** Guest11443 is now known as mgagne | 20:57 | |
*** mgagne has quit IRC | 20:57 | |
*** mgagne has joined #openstack-operators | 20:57 | |
*** dminer has quit IRC | 21:00 | |
*** dminer has joined #openstack-operators | 21:01 | |
*** tongli has quit IRC | 21:02 | |
*** raalee has quit IRC | 21:03 | |
*** TxGirlGeek has quit IRC | 21:03 | |
*** paramite has joined #openstack-operators | 21:12 | |
*** emagana has joined #openstack-operators | 21:12 | |
*** dfflanders has joined #openstack-operators | 21:26 | |
*** racedo has quit IRC | 21:29 | |
*** sdake_ has joined #openstack-operators | 21:33 | |
*** dminer has quit IRC | 21:38 | |
*** paramite has quit IRC | 21:39 | |
*** VW has quit IRC | 21:40 | |
*** paramite has joined #openstack-operators | 21:42 | |
*** slaweq_ has quit IRC | 21:49 | |
*** chlong has quit IRC | 21:50 | |
*** slaweq_ has joined #openstack-operators | 21:54 | |
mrhillsman | eset | 22:02 |
*** dminer has joined #openstack-operators | 22:03 | |
*** sdake_ has quit IRC | 22:05 | |
*** _ducttape_ has quit IRC | 22:07 | |
*** VW has joined #openstack-operators | 22:08 | |
*** paramite has quit IRC | 22:08 | |
*** VW has quit IRC | 22:13 | |
*** catintheroof has joined #openstack-operators | 22:15 | |
*** TxGirlGeek has joined #openstack-operators | 22:20 | |
*** sorrison_ has quit IRC | 22:29 | |
*** slaweq_ has quit IRC | 22:29 | |
*** emagana has quit IRC | 22:31 | |
*** slaweq_ has joined #openstack-operators | 22:31 | |
*** VW has joined #openstack-operators | 22:33 | |
*** emagana has joined #openstack-operators | 22:33 | |
*** sdake has joined #openstack-operators | 22:33 | |
*** emagana_ has joined #openstack-operators | 22:35 | |
*** emagana has quit IRC | 22:35 | |
*** _ducttape_ has joined #openstack-operators | 22:36 | |
*** slaweq_ has quit IRC | 22:38 | |
*** slaweq_ has joined #openstack-operators | 22:40 | |
*** mriedem has quit IRC | 22:44 | |
*** emagana_ has quit IRC | 22:46 | |
*** emagana has joined #openstack-operators | 22:48 | |
*** jamesdenton has quit IRC | 22:49 | |
*** _ducttape_ has quit IRC | 22:50 | |
*** VW has quit IRC | 22:51 | |
*** VW has joined #openstack-operators | 22:51 | |
*** _ducttape_ has joined #openstack-operators | 22:52 | |
*** emagana has quit IRC | 22:53 | |
*** emagana has joined #openstack-operators | 22:55 | |
*** marst has quit IRC | 22:56 | |
*** Apoorva has quit IRC | 23:03 | |
*** Apoorva has joined #openstack-operators | 23:04 | |
*** VW_ has joined #openstack-operators | 23:07 | |
*** VW has quit IRC | 23:10 | |
*** VW_ has quit IRC | 23:11 | |
*** saneax-_-|AFK is now known as saneax | 23:16 | |
*** VW has joined #openstack-operators | 23:21 | |
*** gfhellma has quit IRC | 23:22 | |
*** gfhellma has joined #openstack-operators | 23:23 | |
*** VW has quit IRC | 23:25 | |
*** dminer has quit IRC | 23:32 | |
*** cdelatte has quit IRC | 23:36 | |
*** rcernin has quit IRC | 23:41 | |
*** catintheroof has quit IRC | 23:44 | |
*** ShaneR_ has joined #openstack-operators | 23:44 | |
*** gfhellma_ has joined #openstack-operators | 23:51 | |
*** gfhellma has quit IRC | 23:53 | |
*** _ducttape_ has quit IRC | 23:58 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!