Menu
▾
▴
opennode-users
|
From: <ope...@li...> - 2014-09-08 15:01:19
|
All, I'm new to the opennode list, but have been doing virtualization with Xen for more than 7 years. We are a Linux-only shop, and the low overhead of openvz containers was a draw for switching to that platform, and we chose opennode for its ease of implementation and use. We have our first opennode server up and running and I'm already extremely impressed with the performance and the command line tools are stellar. We don't really need the opennode manger web gui, but since it was available to install within opennode, we thought we would give that a try. We installed it and attached the VM's to the console and everything was fine for a time, then two things have happened in rapid succession to each other: * First, the opennode manager host machine just shows spinning as if trying to update in the VM listing, but the VM's still showed * Second, the opennode manager host machine shows spinning as if trying to update but now NO VM's are showing. All of the VM containers are up and working so it is not mission critical at all, but we would like to get the web gui working as well if we can. Has anyone else run into this? We /have/ updated the OMS via the command line: /opt/oms/update.sh && service oms restart but that has done nothing to fix the issue. Thanks, -- -- Steven G. Spencer, Network Administrator KSC Corporate - The Kelly Supply Family of Companies Office 308-382-8764 Ext. 1131 Mobile 402-765-8010 |
|
From: <ope...@li...> - 2014-09-08 16:16:15
|
Hi Steven, The current situation with OMS is that its not anymore in active development - and in its current form it might need some tweaking in order to get it running - as we never released fully stable OMS for OpenNode 6. However we still have it running on couple of production installations - just we didnt had time or resources to stabilize and package OMS for general availability. Lot of issues were related to saltstack version we were using back then - and it hasnt been updated to latest saltstack - which might perform better now with OMS (but probably needs some dev work for update). We are working actively on OMS successor - but its currently only for early adopters with targeted dev projects - not sure when it reaches GA. So in short - I would not recommend to rely on OMS - unless you get it running :-) We have OMS running with WHMCS billing for simple Cloud Provider setup - but it probably needs a bit our support hours in order to replicate or package/stabilize for GA release - ie we dont have free resources for that unless its going through our commercial support channel. Or if there would be anybody from community who would be interested of updating and stabilizing OMS - we could provide some OMS internals know-how support in commentary form - in order to assist with that task. Hint: there are some OMS internals info in OpenNode wiki which might help. Regarding your OMS symptoms - I would say its probably OMS/Salt sync action with host - that got stuck for some reason. OMS VM restart does not help? salt-minion restart on OpenNode OS host? Regards, -- <http://www.getpostbox.com>---------------------------------------------- Andres Toomsalu,an...@op... <mailto:an...@op...> http://www.opennodecloud.com <http://www.opennodecloud.com/> > ope...@li... > <mailto:ope...@li...> > 8. september 2014 18:01 > All, > > I'm new to the opennode list, but have been doing virtualization with > Xen for more than 7 years. We are a Linux-only shop, and the low > overhead of openvz containers was a draw for switching to that > platform, and we chose opennode for its ease of implementation and use. > > We have our first opennode server up and running and I'm already > extremely impressed with the performance and the command line tools > are stellar. We don't really need the opennode manger web gui, but > since it was available to install within opennode, we thought we would > give that a try. > > We installed it and attached the VM's to the console and everything > was fine for a time, then two things have happened in rapid succession > to each other: > > * First, the opennode manager host machine just shows spinning as if > trying to update in the VM listing, but the VM's still showed > * Second, the opennode manager host machine shows spinning as if > trying to update but now NO VM's are showing. > > All of the VM containers are up and working so it is not mission > critical at all, but we would like to get the web gui working as well > if we can. > > Has anyone else run into this? We /have/ updated the OMS via the > command line: > > /opt/oms/update.sh && service oms restart > but that has done nothing to fix the issue. > > Thanks, > > -- > -- > Steven G. Spencer, Network Administrator > KSC Corporate - The Kelly Supply Family of Companies > Office 308-382-8764 Ext. 1131 > Mobile 402-765-8010 > ------------------------------------------------------------------------------ > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce > Perforce version control. Predictably reliable. > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > _______________________________________________ > OpenNode-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennode-users |
|
From: <ope...@li...> - 2014-09-08 16:54:24
|
Andres, Well that is good enough for me. Thanks very much for the quick reply. We will either hold off running OMS for now or live with the bugs. Again, not a huge deal, as OpenNode is fully functional without it. Thanks again! Steve On 09/08/2014 10:44 AM, ope...@li... wrote: > Hi Steven, > > The current situation with OMS is that its not anymore in active > development - and in its current form it might need some tweaking in > order to get it running - as we never released fully stable OMS for > OpenNode 6. However we still have it running on couple of production > installations - just we didnt had time or resources to stabilize and > package OMS for general availability. Lot of issues were related to > saltstack version we were using back then - and it hasnt been updated > to latest saltstack - which might perform better now with OMS (but > probably needs some dev work for update). We are working actively on > OMS successor - but its currently only for early adopters with > targeted dev projects - not sure when it reaches GA. > > So in short - I would not recommend to rely on OMS - unless you get it > running :-) We have OMS running with WHMCS billing for simple Cloud > Provider setup - but it probably needs a bit our support hours in > order to replicate or package/stabilize for GA release - ie we dont > have free resources for that unless its going through our commercial > support channel. > > Or if there would be anybody from community who would be interested of > updating and stabilizing OMS - we could provide some OMS internals > know-how support in commentary form - in order to assist with that > task. Hint: there are some OMS internals info in OpenNode wiki which > might help. > > Regarding your OMS symptoms - I would say its probably OMS/Salt sync > action with host - that got stuck for some reason. OMS VM restart does > not help? salt-minion restart on OpenNode OS host? > > Regards, > -- > <http://www.getpostbox.com>---------------------------------------------- > > Andres Toomsalu,an...@op... <mailto:an...@op...> > > http://www.opennodecloud.com <http://www.opennodecloud.com/> > > > >> ope...@li... >> <mailto:ope...@li...> >> 8. september 2014 18:01 >> All, >> >> I'm new to the opennode list, but have been doing virtualization with >> Xen for more than 7 years. We are a Linux-only shop, and the low >> overhead of openvz containers was a draw for switching to that >> platform, and we chose opennode for its ease of implementation and use. >> >> We have our first opennode server up and running and I'm already >> extremely impressed with the performance and the command line tools >> are stellar. We don't really need the opennode manger web gui, but >> since it was available to install within opennode, we thought we >> would give that a try. >> >> We installed it and attached the VM's to the console and everything >> was fine for a time, then two things have happened in rapid >> succession to each other: >> >> * First, the opennode manager host machine just shows spinning as if >> trying to update in the VM listing, but the VM's still showed >> * Second, the opennode manager host machine shows spinning as if >> trying to update but now NO VM's are showing. >> >> All of the VM containers are up and working so it is not mission >> critical at all, but we would like to get the web gui working as well >> if we can. >> >> Has anyone else run into this? We /have/ updated the OMS via the >> command line: >> >> /opt/oms/update.sh && service oms restart >> but that has done nothing to fix the issue. >> >> Thanks, >> >> -- >> -- >> Steven G. Spencer, Network Administrator >> KSC Corporate - The Kelly Supply Family of Companies >> Office 308-382-8764 Ext. 1131 >> Mobile 402-765-8010 >> ------------------------------------------------------------------------------ >> Want excitement? >> Manually upgrade your production database. >> When you want reliability, choose Perforce >> Perforce version control. Predictably reliable. >> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk >> _______________________________________________ >> OpenNode-users mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/opennode-users > > > > > ------------------------------------------------------------------------------ > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce > Perforce version control. Predictably reliable. > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > > > _______________________________________________ > OpenNode-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennode-users |
|
From: <ope...@li...> - 2014-09-08 17:36:46
|
Thats the case of OpenNode currently - its more of a lightweight "lego" platform to build your customized solutions on top - regarding higher level management and orchestration. OMS idea itself was nice - it was designed as a stateless controller with two-way sync - reflecting actual system state and (also manual) system changes - not being database centric and non-coherent to reality. Sadly sync layer underneath was a bit error-prone - and needs updating/stabilizing. Actually if you look deeper - OMS can do much more in CLI (ssh session to 6022 port) - than through WUI. Some CLI documentation exists in the wiki: * https://support.opennodecloud.com/wiki/doku.php?id=usrdoc:oms:omsh * https://support.opennodecloud.com/wiki/doku.php?id=usrdoc:oms:omshcommands We are lacking proper docs - but there are some bits and pieces... As for debugging OMS: https://support.opennodecloud.com/wiki/doku.php?id=devdoc:oms:omsdebug > ope...@li... > <mailto:ope...@li...> > 8. september 2014 19:52 > Andres, > > Well that is good enough for me. Thanks very much for the quick reply. > We will either hold off running OMS for now or live with the bugs. > Again, not a huge deal, as OpenNode is fully functional without it. > > Thanks again! > Steve > > On 09/08/2014 10:44 AM, ope...@li... wrote: > > ------------------------------------------------------------------------------ > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce > Perforce version control. Predictably reliable. > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > _______________________________________________ > OpenNode-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennode-users > Andres Toomsalu <mailto:an...@op...> > 8. september 2014 18:44 > Hi Steven, > > The current situation with OMS is that its not anymore in active > development - and in its current form it might need some tweaking in > order to get it running - as we never released fully stable OMS for > OpenNode 6. However we still have it running on couple of production > installations - just we didnt had time or resources to stabilize and > package OMS for general availability. Lot of issues were related to > saltstack version we were using back then - and it hasnt been updated > to latest saltstack - which might perform better now with OMS (but > probably needs some dev work for update). We are working actively on > OMS successor - but its currently only for early adopters with > targeted dev projects - not sure when it reaches GA. > > So in short - I would not recommend to rely on OMS - unless you get it > running :-) We have OMS running with WHMCS billing for simple Cloud > Provider setup - but it probably needs a bit our support hours in > order to replicate or package/stabilize for GA release - ie we dont > have free resources for that unless its going through our commercial > support channel. > > Or if there would be anybody from community who would be interested of > updating and stabilizing OMS - we could provide some OMS internals > know-how support in commentary form - in order to assist with that > task. Hint: there are some OMS internals info in OpenNode wiki which > might help. > > Regarding your OMS symptoms - I would say its probably OMS/Salt sync > action with host - that got stuck for some reason. OMS VM restart does > not help? salt-minion restart on OpenNode OS host? > > Regards, > -- > <http://www.getpostbox.com>---------------------------------------------- > > Andres Toomsalu,an...@op... <mailto:an...@op...> > > http://www.opennodecloud.com <http://www.opennodecloud.com/> > > > > > ope...@li... > <mailto:ope...@li...> > 8. september 2014 18:01 > All, > > I'm new to the opennode list, but have been doing virtualization with > Xen for more than 7 years. We are a Linux-only shop, and the low > overhead of openvz containers was a draw for switching to that > platform, and we chose opennode for its ease of implementation and use. > > We have our first opennode server up and running and I'm already > extremely impressed with the performance and the command line tools > are stellar. We don't really need the opennode manger web gui, but > since it was available to install within opennode, we thought we would > give that a try. > > We installed it and attached the VM's to the console and everything > was fine for a time, then two things have happened in rapid succession > to each other: > > * First, the opennode manager host machine just shows spinning as if > trying to update in the VM listing, but the VM's still showed > * Second, the opennode manager host machine shows spinning as if > trying to update but now NO VM's are showing. > > All of the VM containers are up and working so it is not mission > critical at all, but we would like to get the web gui working as well > if we can. > > Has anyone else run into this? We /have/ updated the OMS via the > command line: > > /opt/oms/update.sh && service oms restart > but that has done nothing to fix the issue. > > Thanks, > > -- > -- > Steven G. Spencer, Network Administrator > KSC Corporate - The Kelly Supply Family of Companies > Office 308-382-8764 Ext. 1131 > Mobile 402-765-8010 > ------------------------------------------------------------------------------ > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce > Perforce version control. Predictably reliable. > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > _______________________________________________ > OpenNode-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennode-users |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X