Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel-dev, 2016-03-01

| Channels | #fuel-dev index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:28 dshulyak joined #fuel-dev
00:58 zigo angdraug: Around? You're not replying on Skype...
01:01 angdraug zigo: I am now, thanks for the ping )
01:15 zigo angdraug: I can hear you, seems you can't hear me.
01:37 xarses joined #fuel-dev
02:08 dims joined #fuel-dev
02:17 dims joined #fuel-dev
04:49 krobzaur joined #fuel-dev
05:35 javeriak joined #fuel-dev
05:40 javeriak joined #fuel-dev
05:42 javeriak_ joined #fuel-dev
06:23 e0ne joined #fuel-dev
06:28 fzhadaev joined #fuel-dev
06:33 e0ne joined #fuel-dev
06:54 javeriak joined #fuel-dev
07:02 dshulyak joined #fuel-dev
07:41 ddepaoli joined #fuel-dev
07:47 amnk joined #fuel-dev
08:16 bhaskarduvvuri joined #fuel-dev
08:18 HeOS joined #fuel-dev
08:22 salmon_ joined #fuel-dev
08:28 rvyalov_ joined #fuel-dev
08:28 zubchick joined #fuel-dev
08:30 bhaskarduvvuri joined #fuel-dev
08:37 ekosareva joined #fuel-dev
08:39 _nadya_ joined #fuel-dev
09:09 amnk joined #fuel-dev
09:20 igajsin1 left #fuel-dev
09:23 enikher joined #fuel-dev
09:26 zigo kozhukalov: Hi there!
09:27 zigo kozhukalov: Are you around?
09:28 e0ne joined #fuel-dev
09:30 ddmitriev joined #fuel-dev
09:49 aarefiev joined #fuel-dev
09:59 kaliya joined #fuel-dev
10:03 kozhukalov zigo: here
10:03 zigo kozhukalov: How's going your packaged based install of the master node on CentOS ?
10:04 kozhukalov it is merged
10:04 zigo kozhukalov: Ah, really? Cool! :)
10:04 zigo kozhukalov: I'm soon to have something for Debian now.
10:05 kozhukalov but it still need some alignment
10:05 zigo kozhukalov: IBP works, then the OS reboots under the installed system, the last issue that I had was root=UUID=<uuid> preventing the OS to boot, so i just patched fuel-agent to not append it.
10:05 zigo kozhukalov: I'm currently reinstalling and retrying, and see if it goes further! :)
10:06 zigo kozhukalov: What did you do for the javascript? Just used a bundled stuff?
10:06 zigo kozhukalov: It's on my todo list to package each and every individual lib, including gulp itself, so that there's a remote chance that I can upload it to Debian.
10:07 zigo kozhukalov: Though currently, I'm using a fuel-web-bundled-js source package hacked with npm install / gulp build, until I can prove everything works.
10:08 zigo kozhukalov: After cloud-init is launched on the slave node, what's next to happen?
10:09 zigo kozhukalov: Puppet stuff orchestrated by astute + mcollective directly?
10:10 zigo Or is there another stage?
10:11 zigo kozhukalov: Also, as cloud-init starts, what is actually answering its call on the network?
10:11 e0ne joined #fuel-dev
10:14 kozhukalov zigo: for javascript yes, we have a huge bundle
10:16 kozhukalov zigo: cloud-init does some basic configuration and then once nailgun-agent reports to the master node that it is back online, nailgun starts openstack deployment tasks
10:16 kozhukalov zigo: yes, it is "Puppet stuff orchestrated by astute + mcollective"
10:17 zigo kozhukalov: What basic config is cloud-init doing?
10:18 kozhukalov zigo: cloud-init does not request any metadata service, instead it uses nocloud data source (a partition in the end of first hard drive)
10:19 zigo kozhukalov: What's the point of running cloud-init then?
10:19 kozhukalov zigo: just network, ntp, puppet, mcollective
10:19 kozhukalov https://github.com/openstack/fuel-agent/tree/master/cloud-init-templates
10:19 zigo Yeah, I saw them, one issue is that I had to do a copy of the ubuntu ones, with "debian" in the name! :)
10:20 kozhukalov https://github.com/openstack/fuel-agent/blob/master/cloud-init-templates/boothook_fuel_8.0_ubuntu.jinja2 and https://github.com/openstack/fuel-agent/blob/master/cloud-init-templates/cloud_config_fuel_8.0_ubuntu.jinja2
10:20 zigo Otherwise, fuel-agent would fail to provision.
10:20 zigo This was fun.
10:20 zigo Though I don't really understand what these are for! :)
10:21 kozhukalov you are right, we need to improve this
10:23 zigo kozhukalov: I wasn't able to switch operating_system: "Ubuntu" to operating_system: "Debian" in openstack.yaml in nailgun, if do, then the UI stops working (ie: if I click on "Dashboard" then it doesn't work, and the UI is completely iresponsive after that).
10:23 zigo So I left it ...
10:24 zigo kozhukalov: I also didn't find a way to replace the "ubuntu_bootstrap" profile by "debian_bootstrap" in Cobbler ! :P
10:24 zigo Though even without these, things work ... :D
10:34 openstackstatus NOTICE: Gerrit is going to be restarted due to poor performance
10:34 Topic for #fuel-dev is now Gerrit is going to be restarted due to poor performance
10:40 Topic for #fuel-dev is now Fuel Development http://wiki.openstack.org/wiki/Fuel | Paste here http://paste.openstack.org/ | IRC logs http://irclog.perlgeek.de/fuel-dev/ | gerrit traffic @ #fuel-tracker
10:40 openstackstatus NOTICE: gerrit finished restartign
10:42 zigo kozhukalov: One thing I don't really understand, is why I'm not getting anything in the "logs" tab. How is this fetched? When do I start to get some data over there?
10:43 zigo kozhukalov: Could it be a unix access rights issue?
10:46 kozhukalov zigo: most likely it is path to logs
10:46 zigo kozhukalov: I do have the /var/log/remote folder created, and nailgun even write folders and symlinks there.
10:46 zigo But it always stays empty.
10:46 zigo No idea why...
10:56 kozhukalov zigo: check rsyslog is configured properly
10:57 kozhukalov we use puppet to configure it
10:57 zigo kozhukalov: You mean on the master node ?
10:57 kozhukalov but you use shell deployment script
10:57 kozhukalov so you need to backport this rsyslog puppet manifest
10:57 kozhukalov yes, on the master node
10:58 zigo kozhukalov: Yeah, though the script is amazingly small, and only contains things which can't be written within the packages.
10:58 kozhukalov https://github.com/openstack/fuel-library/blob/master/deployment/puppet/fuel/examples/rsyslog.pp
10:59 zigo Yeaaaaaaaah ! This time my slave nodes rebooted on the HDD under Debian after the IBP installation ! :)
10:59 zigo \o/
11:01 kozhukalov zigo: that is awesome
11:01 kozhukalov so, the only step left is to deploy openstack
11:03 zigo kozhukalov: Yup, and normally, all of puppet upstream is fixed to understand Debian.
11:03 zigo kozhukalov: I also need to setup puppet-master on the master node no?
11:03 zigo I haven't touched that yet ...
11:03 dims joined #fuel-dev
11:04 zigo kozhukalov: I also packaged all of the puppet modules we use in fuel-library (they are all in Debian Sid already), so it's just a mater of getting the upgrades to Mitaka done.
11:04 zigo 2016-03-01 11:04:34 DEBUG [8715] Not target nodes will be rejected:
11:04 zigo 2016-03-01 11:04:34 DEBUG [8715] Not provisioned: 1,2, got target OSes:
11:04 zigo 2016-03-01 11:04:34 DEBUG [8715] Still provisioning following nodes: ["1", "2"]
11:04 zigo 2016-03-01 11:04:34 DEBUG [8715] Can't read file with logs: /var/log/remote/node-1.domain.tld/bootstrap/fuel-agent.log
11:04 zigo 2016-03-01 11:04:34 DEBUG [8715] Can't read file with logs: /var/log/remote/node-2.domain.tld/bootstrap/fuel-agent.log
11:05 zigo I wonder what's that mean ...
11:05 zigo kozhukalov: I'm not seeing anything happening, where should I look now?
11:06 kozhukalov zigo, fuel does not use puppet master, instead we rsync modules on slaves and then run puppet apply using mcollective
11:06 zigo Oh, I thought we moved away from masterless puppet...
11:06 zigo Wasn't this planned at some point?
11:07 zigo Hum... "mco ping" in the master node replies nothing but "master".
11:07 zigo Something must have gone wrong in the mcollective setup of the slave nodes.
11:07 kozhukalov zigo, that is also awesome that you have packaged fuel-library modules into deb packages because it allows us to deliver puppet modules on slaves using packages instead of rsyncing them
11:08 zigo Ah, good point! :)
11:08 zigo kozhukalov: FYI, they all end-up in /usr/share/modules, I'm not sure if that's ok with puppet, but I saw other packages in Debian doing that.
11:08 zigo kozhukalov: Worst case, we'd do symlinks in /etc/puppet/modules.
11:09 kozhukalov zigo, that is ok to put them in /usr/share because we can easily create a link /etc/puppet/modules -> /usr/share/modules
11:09 zigo kozhukalov: My /etc/apt/sources.list is empty in the slave nodes, after the reboot on the HDD, is this expected?
11:10 kozhukalov zigo: is there anything in /etc/apt/sources.list.d ?
11:10 zigo kozhukalov: Nop, nothing.
11:11 kozhukalov zigo, ahh yes, it is as expected
11:11 kozhukalov zigo, it is one of deployment tasks to cofigure repos
11:11 kozhukalov as far as i remember
11:12 zigo kozhukalov: Oh, I know what's wrong, "daemonize=0" in /etc/mcollective/server.cfg...
11:12 zigo It should be set to 1 in Debian, IIRC.
11:13 zigo Hum... still no mco ping ... :/
11:18 kozhukalov zigo: is /etc/mcollective/server.cfg corresponds to https://github.com/openstack/fuel-agent/blob/master/cloud-init-templates/cloud_config_fuel_8.0_ubuntu.jinja2#L44-L73 ?
11:18 zigo Oh, thanks !
11:18 kozhukalov i mean master node ip, key, id and so on? are they correct?
11:19 zigo You mean identity =?
11:20 zigo It seems correct yes.
11:24 zigo Found it!
11:24 salmon_1 joined #fuel-dev
11:24 zigo "direct_addressing" shouldn't be set
11:24 zigo kozhukalov: What's "direct_addressing" for?
11:37 kozhukalov zigo: to avoid broadcasting
11:37 kozhukalov zigo: that is better if you run recent version of mcollective
11:50 zubchick joined #fuel-dev
12:36 zinovik joined #fuel-dev
12:36 bhaskarduvvuri joined #fuel-dev
12:48 jaypipes joined #fuel-dev
12:52 zubchick joined #fuel-dev
12:55 zubchick joined #fuel-dev
12:56 zigo I get: {"uid"=>"1", "progress"=>100, "status"=>"provisioned"} in astute log! :)
12:57 zigo (not the other one because it timed out when I was having dinner...)
12:59 zigo Ok, let's start over a new deployment with the mcollective fixes in the .jinja2, and let's see if it goes up to the end! :P
13:05 ekosareva joined #fuel-dev
13:08 dims joined #fuel-dev
13:30 zigo kozhukalov: Modules shall be installed in /etc/puppet/modules, and not /etc/puppet/mitaka-9.0, right? I have conflicting informations...
13:40 bpiotrowski on master node, /etc/puppet/modules is symlink to latest release
13:41 zigo bpiotrowski: Ah, I see...
13:41 zigo Thanks.
13:41 zigo I'll push directly to /etc/puppet/modules for the moment then (configurable in debian/rules).
13:41 bpiotrowski I mean, current centos one, because I guess you're talking about making it Debian
13:46 zigo Yup. :P
13:46 zigo My last run went to puppet, and failed because it didn't find modules in /etc/puppet/modules.
13:46 zigo So I'm pushing all in there.
13:47 zigo I'm sure it's going to fail because I haven't packaged Mitaka openstack-puppet yet (it's still using the 7.0 Liberty tag for these modules).
13:47 zigo But never mind.
13:50 zubchick joined #fuel-dev
13:59 amnk joined #fuel-dev
14:03 bpiotrowski yeah, I guess it will
14:05 bhaskarduvvuri joined #fuel-dev
14:13 bhaskarduvvuri joined #fuel-dev
14:13 kozhukalov zigo: we usually have several versions of modules on the master node (like /etc/puppet/v1, /etc/puppet/v2), but /etc/puppet/modules refers to the version that is used on the master node (for master node deployment). When puppet modules are rsynced on slaves for openstack deployment, nailgun by default uses /etc/puppet/modules, but also a particular version
14:13 kozhukalov e.g. /etc/puppet/v2 can be used https://github.com/openstack/fuel-web/blob/master/nailgun/nailgun/fixtures/openstack.yaml#L1453
14:53 zigo kozhukalov: I've done what you've suggested, and added fuel-library to the IBP image (ie: in openstack.yaml, which in my case is debian.yaml until I get my changes upstreamed), meaning it's going to be there even without doing rsync.
14:57 zigo kozhukalov: Now, since we can use package, I wonder how we could make it in a clean way so we store multiple versions of puppet-openstack. One way I thought about is having versionned puppet module, for example "puppet-module-nova-liberty" and "puppet-module-nova-mitaka", which would be stored in /usr/share/puppet/modules-available, with the normal update-alternatives stuff. The only issue is that this will force all of these modules to go through the Debian
14:57 zigo FTP master NEW queue once per release, and they wont like me for that at all. Also, it doesn't really make sense to do such a thing to upload in Debian, since only a single version of OpenStack can be uploaded per Debian release. So probably that's something we should think only for the commercial version of the Fuel ISO image.
14:57 skolekonov_ joined #fuel-dev
14:57 zigo Let's keep that aside for the moment.
14:57 zigo I'll open a new thread on the list.
14:58 zigo Is there any rsyslog configuration specialist over here?
14:58 zigo kozhukalov: Are you good with it?
14:59 zigo In the Fuel ISO, there's /etc/rsyslog.d/server.conf, which looks like very much CentOS centric to me, with such a thing as /var/log/message. So, there's that, and I also have the concern that rsyslog would open on a public interface, which would be a kind of security hole if it has a public IP address. So, I'm a little bit scared to have this default server.conf shipped directly in nailgun-common. I'm open for any suggestion...
15:00 zigo Oh, btw, no reason at all to use puppet for this. It's very much a static file, so we can just store it in a package, then have rsyslog restart in nailgun-common.postisnt (which I have already done).
15:00 zigo Unless someone tells me there's any dynamic value there? (like a password? I didn't spot one...)
15:16 zubchick joined #fuel-dev
15:29 kozhukalov >>> since only a single version of OpenStack can be uploaded per Debian release >>> that is still not a good reason to limit a user by only one release, because no matter on which OS you run fuel itself, it can be used to deploy openstack on various distributions, but you are right, let's leave this aside until we are ready to re-consider this
15:29 brain461 joined #fuel-dev
15:29 kozhukalov about rsyslog, i am not a good specialist here, but i believe there is nothing difficult about rsyslog
15:30 kozhukalov just take a template from the fuel puppet module and fill it in with your values (debian centric values)
15:32 kozhukalov yes, I prefer debianized fuel to avoid using puppet for fuel deployment (at least as a default option)
15:33 kozhukalov about public ip, yes, perhaps it is better to bind it on admin IP, feel free to change this
15:34 kozhukalov what is important is that slaves could send log messages to this IP
15:34 kozhukalov zigo ^^
15:35 zigo kozhukalov: As much as I can see, there's no way to filter with rsyslog itself, so I'm going to firewall it.
15:36 javeriak joined #fuel-dev
15:36 mwhahaha thats how it's handled today via iptables
15:37 gariveradlt joined #fuel-dev
15:39 zigo mwhahaha: Hi there! :)
15:39 kozhukalov zigo, https://github.com/openstack/fuel-library/blob/master/deployment/puppet/fuel/examples/host.pp#L133-L137
15:39 kozhukalov https://github.com/openstack/fuel-library/blob/master/deployment/puppet/fuel/manifests/iptables.pp
15:39 zubchick joined #fuel-dev
15:39 kozhukalov https://github.com/openstack/fuel-library/blob/master/deployment/puppet/fuel/manifests/iptables.pp#L152-L166
15:41 zigo IMO, postgress shouldn't even listen on the network, and nailgun should be using a socket file (plus running as nailgun:nailgun user, since it has no reason to run as root).
15:42 kozhukalov zigo, right
15:42 kozhukalov but don't forget to configure pg_hba.conf
15:42 zigo What's that?
15:43 kozhukalov if you are going to use socket then you should configure properly /etc/postgresql/9.3/main/pg_hba.conf
15:43 kozhukalov it is very well documented
15:44 zigo kozhukalov: It works already with socket files for me in Debian! :)
15:44 kozhukalov ahh, ok, then
15:44 zigo And also, it only accepts auth from the nailgun system user.
15:44 zigo Which is super nice.
15:45 zigo No need to even care about passwords.
15:47 kozhukalov but remember there are couple other services that use postgresql
15:47 kozhukalov ostf and keystone
15:47 kozhukalov zigo ^ and https://github.com/openstack/fuel-library/blob/master/deployment/puppet/fuel/examples/postgresql.pp#L5-L17
15:48 zigo I'm using MySQL for Keystone.
15:48 zigo And I haven't worked out OSTF yet.
15:49 kozhukalov zigo: is there a good reason to run 2 RDBMS (mysql and postgresql) instead of just one (postgresql)?
15:50 zigo kozhukalov: Lazyness and re-used of already written scripts! :)
15:50 zubchick joined #fuel-dev
15:50 zigo This should be fixed at some point.
15:51 zigo IMO, it'd be nice if Fuel could support MySQL through Alembic / SQLA as well btw.
15:55 javeriak joined #fuel-dev
15:59 javeriak_ joined #fuel-dev
16:02 xarses joined #fuel-dev
16:03 xarses joined #fuel-dev
16:13 e0ne joined #fuel-dev
16:13 jaypipes joined #fuel-dev
16:22 zubchick joined #fuel-dev
16:27 zigo kozhukalov: Now, I get rsyslog to work with remote nodes, however, it looks like nailgun can't read it in my machine, since it's not running as root.
16:27 zigo Hard to tell though...
16:29 _nadya_ joined #fuel-dev
16:29 zigo mwhahaha: Astute fails to puppet deploy my master node: http://paste.debian.net/410684/
16:29 zigo I didn't expect such an early failure... :(
16:30 mwhahaha check the puppet log for node 1
16:31 zigo mwhahaha: Where are they?
16:31 mwhahaha in /var/log/remote/node-1*/puppet.log
16:31 mwhahaha or on the node itself in /var/log/puppet.log
16:32 zigo mwhahaha: puppet-agent.log no ?
16:32 mwhahaha yea
16:32 zigo mwhahaha: 2016-03-01T16:17:47.679861+00:00 notice: Reopening log files
16:32 zigo 2016-03-01T16:17:48.333549+00:00 err: Could not request certificate: SIGTERM
16:32 zigo That's it, only these 2 lines.
16:33 mwhahaha that doesn't seem right
16:33 zigo Indeed !
16:33 mwhahaha there should be a bunch of logs from the previous tasks
16:34 igajsin joined #fuel-dev
16:36 zigo mwhahaha: where should I look then?
16:36 mwhahaha was that on the node or did you look on the fuel master?
16:36 zigo Can I try issuing some commands from the master node somehow?
16:36 zigo On the fuel master node.
16:36 mwhahaha check on the node itself (as your rsyslog config may not be correct)
16:36 zigo Because syslog is configured to log remotely, there's nothing in the local node.
16:36 mwhahaha there should be local stuff
16:37 zigo mwhahaha: In /var/log/puppet?
16:37 zigo Nop, no file there...
16:37 mwhahaha no /var/log/puppet.log
16:37 zigo mwhahaha: Yes, but it's an empty file.
16:37 zigo 0 byte.
16:38 mwhahaha on the node itself try running '/usr/sbin/daemonize -a -l /tmp/puppetd.lock            -p /tmp/puppetd.lock  -c / /usr/bin/puppet apply /etc/puppet/modules/osnailyfacter/modular/netconfig/netconfig.pp --modulepath=/etc/puppet/modules --logdest syslog --trace --no-report --debug --evaltrace --logdest /var/log/puppet.log'
16:39 javeriak_ hey guys, quick question, if i change one of the repositories in the Fuel UI, how do I get it to reflect on the nodes? By redploying?
16:39 zigo mwhahaha: -bash: /usr/sbin/daemonize: No such file or directory
16:39 zigo Maybe that's the issue?
16:40 mwhahaha yea that'd be a problem, it should have been included on the image for provisioning
16:40 zigo :)
16:40 e0ne joined #fuel-dev
16:41 zigo mwhahaha: Do you know from where's that program is comming from?
16:41 zigo dpkg -S /usr/sbin/daemonize ?
16:41 mwhahaha i'm in the process of rebuilding my env so i'm not sure at the m oment
16:42 mwhahaha https://github.com/openstack/fuel-web/blob/abf658054d98f8dc2520ad17586c9a07f802679f/nailgun/nailgun/fixtures/openstack.yaml#L1992-L2041
16:42 mwhahaha so that's the package list that should be included in the image to be provisioned
16:42 mwhahaha daemonize is the package name i thought
16:44 zigo mwhahaha: I'm quite sure I have packaged something in ruby that does a daemon stuff... :)
16:45 mwhahaha I think its using daemonize to handle timeouts or something
16:45 mwhahaha not completely sure the history on that one
16:45 zigo Yup: /home/zigo/sources/openstack/fuel/python-daemonize
16:45 zigo :)
16:45 zigo I'll upload that one to Debian soon.
16:45 mwhahaha no daemonize is a c
16:45 mwhahaha app
16:46 mwhahaha http://software.clapper.org/daemonize/
16:46 zigo Oh, python-daemonize is the package name I used !
16:46 zigo It's already in Debian.
16:46 zigo :P
16:47 zigo Though it has nothing in /usr/bin ... :/
16:48 mwhahaha no python-daemonize, daemonize
16:49 mwhahaha https://github.com/bmc/daemonize is the source
16:50 zigo Oh, python-daemonize and daemonize have nothing in common...
16:50 zigo (appart from the name)
16:50 zigo Ok, will package that one.
16:53 zigo Aaaah... A nice stuff in C with autotools and such! :P
16:53 zigo https://www.youtube.com/watch?v=1S1fISh-pag
16:53 zigo (the mandatory one...)
16:56 mwhahaha ha
17:02 kozhukalov mwhahaha: aglarendil could you please review this https://review.openstack.org/286715
17:02 kozhukalov bvt test uses fuel-utils to check if fuel is ready to start deployment
17:08 rmoe_ joined #fuel-dev
17:17 dims_ joined #fuel-dev
17:21 zigo Shit, the ITP has been opened since last July, and nothing was done with it... :/
17:21 zigo https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791857
17:21 zigo I'll package it for myself and write to the bug, see if I can take over the package.
17:26 bhaskarduvvuri joined #fuel-dev
17:34 javeriak_ I'm getting a "500 Server Error: Internal Server Error (u'post_deployment')" on trying to use 'fuel node --node 2 --start post_deployment' ; any help appreciated
17:42 salmon_ joined #fuel-dev
18:13 zigo mwhahaha: 2016-03-01 18:10:12 +0000 Puppet (err): Unsupported OS: /Debian at /etc/puppet/modules/l23network/manifests/params.pp:50 on node node-1.domain.tld
18:13 zigo :)
18:13 zigo Making progress ...
18:13 zigo Now, I believe it's off my hands.
18:13 zigo :P
18:13 mwhahaha yea for now
18:14 zigo I suppose I can send a patch for that one...
18:15 zigo Though do we have lots of them like this?
18:15 zigo mwhahaha: Does (?i) means case insensitive?
18:15 mwhahaha yea
18:16 zigo Funny syntax... :P
18:18 zigo mwhahaha: Is there a way to say "debian or ubuntu" in that file?
18:19 mwhahaha is debian systemd now?
18:20 mwhahaha there's probably more work that needs to get done if it is
18:21 mwhahaha other wise you can update https://github.com/openstack/fuel-library/blob/master/deployment/puppet/l23network/manifests/params.pp#L7 with /(?i)ubuntu|debian/
18:25 zigo mwhahaha: Yeah, it's systemd.
18:25 zigo mwhahaha: Just like the next Ubuntu LTS will.
18:26 zigo mwhahaha: I still get the same error, the leading / is very suspicious.
18:30 aglarendil__ joined #fuel-dev
18:31 ashtokolov_ joined #fuel-dev
18:31 evgenyl_ joined #fuel-dev
18:37 mwhahaha its' a regex
18:37 mwhahaha if it's systemd there's not a quick patch as we basically need to add that support in because ubuntu is upstart
18:39 zigo You know better, I'm giving up! :)
18:48 dims joined #fuel-dev
19:06 ilbot3 joined #fuel-dev
19:06 Topic for #fuel-dev is now Fuel Development http://wiki.openstack.org/wiki/Fuel | Paste here http://paste.openstack.org/ | IRC logs http://irclog.perlgeek.de/fuel-dev/ | gerrit traffic @ #fuel-tracker
19:15 openstackstatus joined #fuel-dev
19:31 maximov_ joined #fuel-dev
19:31 mwhahaha joined #fuel-dev
19:31 yantarou joined #fuel-dev
19:31 sslypushenko joined #fuel-dev
19:31 ikalnitsky joined #fuel-dev
19:31 smakar joined #fuel-dev
19:55 javeriak_ could someone point me to some resources on how to version a fuel plugin, ive read the Plugins wiki already; so all we need to do is change the version in metadata.yml and generate a new tag on the repo?
20:05 javeriak joined #fuel-dev
20:15 javeriak joined #fuel-dev
20:38 e0ne joined #fuel-dev
20:55 e0ne joined #fuel-dev
20:55 zubchick joined #fuel-dev
21:21 angdraug xarses: ^
21:21 angdraug nm, I see he's already got you covered on #fuel )
21:31 dims_ joined #fuel-dev
21:44 dshulyak joined #fuel-dev
21:52 krobzaur joined #fuel-dev
22:10 dims joined #fuel-dev
22:14 dshulyak joined #fuel-dev
23:00 dims joined #fuel-dev
23:32 intr1nsic joined #fuel-dev

| Channels | #fuel-dev index | Today | | Search | Google Search | Plain-Text | summary