You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Mike Tutkowski <mi...@solidfire.com> on 2014/04/07 08:17:15 UTC
[4.4] Current State
Hi,
Sorry for all the e-mails today. I must have spent 6 hours (to no avail)
trying to get 4.4 into a usable state with XenServer or VMware so that I
could demo a 4.4 feature for a customer tomorrow.
Is anyone else experiencing massive issues getting a cloud up and running
with current 4.4?
Perhaps it's my imagination, but it seems for being past feature freeze
that the code should be a lot more reliable.
Thoughts?
Thanks
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*
RE: [4.4] Current State
Posted by Alex Huang <Al...@citrix.com>.
I've reverted it. Commit id ec102ec.
I would have like to have it in 4.4 as it's something we've talked about getting in to get rid of carrying our own copy but if it's causing problems then we should revert it until the problem is fixed.
I apologize for the problem.
--Alex
> -----Original Message-----
> From: Alex Huang [mailto:Alex.Huang@citrix.com]
> Sent: Tuesday, April 8, 2014 12:01 AM
> To: Murali Reddy; dev@cloudstack.apache.org
> Subject: RE: [4.4] Current State
>
> Let's roll this back for now until the right fix is found.
>
> --Alex
>
> > -----Original Message-----
> > From: Murali Reddy
> > Sent: Monday, April 7, 2014 11:42 PM
> > To: dev@cloudstack.apache.org
> > Cc: Alex Huang
> > Subject: Re: [4.4] Current State
> >
> > Is there a workaround? I am blocked on testing 4.4 work.
> >
> > On 07/04/14 8:12 PM, "Konstantina Chremmou"
> > <ko...@citrix.com> wrote:
> >
> > >It seems to me the problem is the xmlrpc dependency of the XAPI jar
> > >rather than the jar itself, as the changes between the previous
> > >version and the latest one do not explain this sort of errors. The
> > >jar we ship depends on 3.1 while cloudstack was using 3.1.3 which
> > >contains several bug fixes compared to the old one. What I can do is
> > >upload a new jar with corrected dependency and submit a new patch.
> > >
> > >
> > >From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
> > >Sent: 07 April 2014 3:06 PM
> > >To: dev@cloudstack.apache.org
> > >Cc: Konstantina Chremmou
> > >Subject: Re: [4.4] Current State
> > >
> > >Now that I think about it, the issue I sent an e-mail regarding
> > >earlier where I could not create an SR (SR.create) only started
> > >happening after the XAPI change.
> > >
> > >Due to this issue, managed storage is currently not functional with
> > >XenServer, which is blocking my 4.4 testing.
> > >
> > >On Mon, Apr 7, 2014 at 5:44 AM, Murali Reddy
> > ><Mu...@citrix.com>> wrote:
> > >Errors I have seen are similar to log's pasted by Sanjay. I am
> > >running into below error while stopping and starting the VM's.
> > >
> > >2014-04-07 13:26:38,960 DEBUG [c.c.h.x.r.CitrixResourceBase]
> > >(DirectAgent-107:ctx-0aa97361) cannot get host enabled status, host
> > >10.147.28.60 due to org.apache.xmlrpc.client.XmlRpcClientException:
> > >Failed to parse servers response: Premature end of file.
> > >org.apache.xmlrpc.client.XmlRpcClientException: Failed to parse
> > >servers
> > >response: Premature end of file.
> > > at
> > >org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcS
> tr
> > ea
> > >mTr
> > >a
> > >nsport.java:177)
> > > at
> > >org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(XmlRpcSt
> re
> > am
> > >Tra
> > >n
> > >sport.java:145)
> > > at
> > >org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest(XmlRpcHttp
> Tr
> > an
> > >spo
> > >r
> > >t.java:94)
> > > at
> > >org.apache.xmlrpc.client.XmlRpcSunHttpTransport.sendRequest(XmlRpcS
> u
> > nHt
> > >tpT
> > >r
> > >ansport.java:44)
> > > at
> > >org.apache.xmlrpc.client.XmlRpcClientWorker.execute(XmlRpcClientWor
> ke
> > r.
> > >jav
> > >a
> > >:53)
> > > at
> > >org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:166)
> > > at
> > >org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:136)
> > > at
> > >org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:125)
> > > at com.xensource.xenapi.Connection.dispatch(Connection.java:330)
> > > at
> > >com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServe
> rC
> > onn
> > >ect
> > >i
> > >on.dispatch(XenServerConnectionPool.java:457)
> > > at com.xensource.xenapi.Host.getEnabled(Host.java:672)
> > > at
> > >com.cloud.hypervisor.xen.resource.CitrixResourceBase.pingXAPI(CitrixR
> > >es
> > >our
> > >c
> > >eBase.java:409)
> > > at
> > >com.cloud.hypervisor.xen.resource.CitrixResourceBase.getCurrentStatus
> > >(C
> > >itr
> > >i
> > >xResourceBase.java:4302)
> > > at
> > >com.cloud.agent.manager.DirectAgentAttache$PingTask.runInContext(Di
> re
> > ct
> > >Age
> > >n
> > >tAttache.java:144)
> > > at
> > >org.apache.cloudstack.managed.context.ManagedContextRunnable$1.ru
> n(
> > Mana
> > >ged
> > >C
> > >ontextRunnable.java:49)
> > > at
> > >org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1
> .c
> > all
> > >(De
> > >f
> > >aultManagedContext.java:56)
> > > at
> > >org.apache.cloudstack.managed.context.impl.DefaultManagedContext.ca
> ll
> > Wi
> > >thC
> > >o
> > >ntext(DefaultManagedContext.java:103)
> > > at
> > >org.apache.cloudstack.managed.context.impl.DefaultManagedContext.ru
> n
> > Wit
> > >hCo
> > >n
> > >text(DefaultManagedContext.java:53)
> > > at
> > >org.apache.cloudstack.managed.context.ManagedContextRunnable.run(
> M
> > anage
> > >dCo
> > >n
> > >textRunnable.java:46)
> > > at
> > >java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> > > at
> > >java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
> > > at
> > >java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
> > >a
> > c
> > >ces
> > >s
> > >$301(ScheduledThreadPoolExecutor.java:178)
> > > at
> > >java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
> > >r
> > u
> > >n(S
> > >c
> > >heduledThreadPoolExecutor.java:293)
> > > at
> > >java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.
> > >ja
> > va:
> > >1
> > >145)
> > > at
> > >java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecuto
> r
> > >.j
> > >ava
> > >:
> > >615)
> > > at java.lang.Thread.run(Thread.java:744)
> > >Caused by: org.xml.sax.SAXParseException; Premature end of file.
> > > at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
> > >Source)
> > > at
> > >org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcS
> tr
> > ea
> > >mTr
> > >a
> > >nsport.java:175)
> > >
> > >
> > >
> > >On 07/04/14 4:51 PM, "Sanjay Tripathi"
> > ><sa...@citrix.com>> wrote:
> > >
> > >>Hi Tina,
> > >>
> > >>Even I am facing similar issues after the change in XAPI. A lot of
> > >>exceptions are coming when CS tries to launch system VMs.
> > >>
> > >>Please find the management server logs at:
> > http://pastebin.com/6s44hDq5.
> > >>
> > >>--Sanjay
> > >>
> > >>-----Original Message-----
> > >>From: Konstantina Chremmou
> > >>[mailto:konstantina.chremmou@citrix.com<mailto:konstantina.chremm
> o
> > u@ci
> > >>tri
> > >>x.com>]
> > >>Sent: Monday, April 7, 2014 4:21 PM
> > >>To: dev@cloudstack.apache.org<ma...@cloudstack.apache.org>
> > >>Subject: RE: [4.4] Current State
> > >>
> > >>Hi Murali,
> > >>
> > >>The latest XAPI jar can be used with older versions of xenserver.
> > >>Could you please specify what are the exact errors you get after
> > >>that
> > commit?
> > >>
> > >>Thanks,
> > >>Tina
> > >>
> > >>> -----Original Message-----
> > >>> From: Mike Tutkowski
> > >>>[mailto:mike.tutkowski@solidfire.com<mailto:mike.tutkowski@solidfir
> e.
> > >>>com
> > >>>>]
> > >>> Sent: 07 April 2014 7:53 AM
> > >>> To: dev@cloudstack.apache.org<ma...@cloudstack.apache.org>
> > >>> Subject: Re: [4.4] Current State
> > >>>
> > >>> XS 6.1
> > >>>
> > >>> On Monday, April 7, 2014, Murali Reddy
> > >>><Mu...@citrix.com>> wrote:
> > >>>
> > >>> >
> > >>> > Are you running XS 6.2? Have not tried latest 4.4, but last week
> > >>> > with plain XenServer 6.2 I am running into several xapi errors
> > >>> > after the commit
> > >>> > 1439c69b7e4396d0b8b26076585c6465e44624f3 to remove XAPI jar.
> > >>> >
> > >>> > I able to run 4.4 with XenServer 6.2 fine with the previous
> > >>> > commit 3ee55cd17b941b1fdb1e0bb150bebfb8ece8155d though.
> > >>> >
> > >>> > On 07/04/14 11:47 AM, "Mike Tutkowski"
> > >>> >
> > >>><mike.tutkowski@solidfire.com<mailto:mike.tutkowski@solidfire.com
> ><
> > ja
> > >>>vas
> > >>>cript:;>
> > >>> > >
> > >>> > wrote:
> > >>> >
> > >>> > >Hi,
> > >>> > >
> > >>> > >Sorry for all the e-mails today. I must have spent 6 hours (to
> > >>> > >no
> > >>> > >avail) trying to get 4.4 into a usable state with XenServer or
> > >>> > >VMware so that I could demo a 4.4 feature for a customer
> tomorrow.
> > >>> > >
> > >>> > >Is anyone else experiencing massive issues getting a cloud up
> > >>> > >and running with current 4.4?
> > >>> > >
> > >>> > >Perhaps it's my imagination, but it seems for being past
> > >>> > >feature freeze that the code should be a lot more reliable.
> > >>> > >
> > >>> > >Thoughts?
> > >>> > >
> > >>> > >Thanks
> > >>> > >
> > >>> > >--
> > >>> > >*Mike Tutkowski*
> > >>> > >*Senior CloudStack Developer, SolidFire Inc.*
> > >>> > >e:
> > >>>mike.tutkowski@solidfire.com<ma...@solidfire.com>
> > >>><javascript:;>
> > >>> > >o: 303.746.7302<tel:303.746.7302> Advancing the way the world
> > >>> > >uses the
> > >>> > >cloud<http://solidfire.com/solution/overview/?video=play>
> > >>> > >*(tm)*
> > >>> > >
> > >>> >
> > >>> >
> > >>> >
> > >>>
> > >>> --
> > >>> *Mike Tutkowski*
> > >>> *Senior CloudStack Developer, SolidFire Inc.*
> > >>> e:
> > >>> mike.tutkowski@solidfire.com<ma...@solidfire.com>
> > >>> o: 303.746.7302<tel:303.746.7302>
> > >>> Advancing the way the world uses the
> > >>> cloud<http://solidfire.com/solution/overview/?video=play>
> > >>> *(tm)*
> > >>
> > >
> > >
> > >
> > >
> > >--
> > >Mike Tutkowski
> > >Senior CloudStack Developer, SolidFire Inc.
> > >e: mike.tutkowski@solidfire.com<ma...@solidfire.com>
> > >o: 303.746.7302
> > >Advancing the way the world uses the
> > >cloud<http://solidfire.com/solution/overview/?video=play>(tm)
> > >
> >
RE: [4.4] Current State
Posted by Alex Huang <Al...@citrix.com>.
Let's roll this back for now until the right fix is found.
--Alex
> -----Original Message-----
> From: Murali Reddy
> Sent: Monday, April 7, 2014 11:42 PM
> To: dev@cloudstack.apache.org
> Cc: Alex Huang
> Subject: Re: [4.4] Current State
>
> Is there a workaround? I am blocked on testing 4.4 work.
>
> On 07/04/14 8:12 PM, "Konstantina Chremmou"
> <ko...@citrix.com> wrote:
>
> >It seems to me the problem is the xmlrpc dependency of the XAPI jar
> >rather than the jar itself, as the changes between the previous version
> >and the latest one do not explain this sort of errors. The jar we ship
> >depends on 3.1 while cloudstack was using 3.1.3 which contains several
> >bug fixes compared to the old one. What I can do is upload a new jar
> >with corrected dependency and submit a new patch.
> >
> >
> >From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
> >Sent: 07 April 2014 3:06 PM
> >To: dev@cloudstack.apache.org
> >Cc: Konstantina Chremmou
> >Subject: Re: [4.4] Current State
> >
> >Now that I think about it, the issue I sent an e-mail regarding earlier
> >where I could not create an SR (SR.create) only started happening after
> >the XAPI change.
> >
> >Due to this issue, managed storage is currently not functional with
> >XenServer, which is blocking my 4.4 testing.
> >
> >On Mon, Apr 7, 2014 at 5:44 AM, Murali Reddy
> ><Mu...@citrix.com>> wrote:
> >Errors I have seen are similar to log's pasted by Sanjay. I am running
> >into below error while stopping and starting the VM's.
> >
> >2014-04-07 13:26:38,960 DEBUG [c.c.h.x.r.CitrixResourceBase]
> >(DirectAgent-107:ctx-0aa97361) cannot get host enabled status, host
> >10.147.28.60 due to org.apache.xmlrpc.client.XmlRpcClientException:
> >Failed to parse servers response: Premature end of file.
> >org.apache.xmlrpc.client.XmlRpcClientException: Failed to parse servers
> >response: Premature end of file.
> > at
> >org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcStr
> ea
> >mTr
> >a
> >nsport.java:177)
> > at
> >org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(XmlRpcStre
> am
> >Tra
> >n
> >sport.java:145)
> > at
> >org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest(XmlRpcHttpTr
> an
> >spo
> >r
> >t.java:94)
> > at
> >org.apache.xmlrpc.client.XmlRpcSunHttpTransport.sendRequest(XmlRpcSu
> nHt
> >tpT
> >r
> >ansport.java:44)
> > at
> >org.apache.xmlrpc.client.XmlRpcClientWorker.execute(XmlRpcClientWorke
> r.
> >jav
> >a
> >:53)
> > at
> >org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:166)
> > at
> >org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:136)
> > at
> >org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:125)
> > at com.xensource.xenapi.Connection.dispatch(Connection.java:330)
> > at
> >com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerC
> onn
> >ect
> >i
> >on.dispatch(XenServerConnectionPool.java:457)
> > at com.xensource.xenapi.Host.getEnabled(Host.java:672)
> > at
> >com.cloud.hypervisor.xen.resource.CitrixResourceBase.pingXAPI(CitrixRes
> >our
> >c
> >eBase.java:409)
> > at
> >com.cloud.hypervisor.xen.resource.CitrixResourceBase.getCurrentStatus(C
> >itr
> >i
> >xResourceBase.java:4302)
> > at
> >com.cloud.agent.manager.DirectAgentAttache$PingTask.runInContext(Dire
> ct
> >Age
> >n
> >tAttache.java:144)
> > at
> >org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(
> Mana
> >ged
> >C
> >ontextRunnable.java:49)
> > at
> >org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.c
> all
> >(De
> >f
> >aultManagedContext.java:56)
> > at
> >org.apache.cloudstack.managed.context.impl.DefaultManagedContext.call
> Wi
> >thC
> >o
> >ntext(DefaultManagedContext.java:103)
> > at
> >org.apache.cloudstack.managed.context.impl.DefaultManagedContext.run
> Wit
> >hCo
> >n
> >text(DefaultManagedContext.java:53)
> > at
> >org.apache.cloudstack.managed.context.ManagedContextRunnable.run(M
> anage
> >dCo
> >n
> >textRunnable.java:46)
> > at
> >java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> > at
> >java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
> > at
> >java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.a
> c
> >ces
> >s
> >$301(ScheduledThreadPoolExecutor.java:178)
> > at
> >java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.r
> u
> >n(S
> >c
> >heduledThreadPoolExecutor.java:293)
> > at
> >java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.ja
> va:
> >1
> >145)
> > at
> >java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.j
> >ava
> >:
> >615)
> > at java.lang.Thread.run(Thread.java:744)
> >Caused by: org.xml.sax.SAXParseException; Premature end of file.
> > at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
> >Source)
> > at
> >org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcStr
> ea
> >mTr
> >a
> >nsport.java:175)
> >
> >
> >
> >On 07/04/14 4:51 PM, "Sanjay Tripathi"
> ><sa...@citrix.com>> wrote:
> >
> >>Hi Tina,
> >>
> >>Even I am facing similar issues after the change in XAPI. A lot of
> >>exceptions are coming when CS tries to launch system VMs.
> >>
> >>Please find the management server logs at:
> http://pastebin.com/6s44hDq5.
> >>
> >>--Sanjay
> >>
> >>-----Original Message-----
> >>From: Konstantina Chremmou
> >>[mailto:konstantina.chremmou@citrix.com<mailto:konstantina.chremmo
> u@ci
> >>tri
> >>x.com>]
> >>Sent: Monday, April 7, 2014 4:21 PM
> >>To: dev@cloudstack.apache.org<ma...@cloudstack.apache.org>
> >>Subject: RE: [4.4] Current State
> >>
> >>Hi Murali,
> >>
> >>The latest XAPI jar can be used with older versions of xenserver.
> >>Could you please specify what are the exact errors you get after that
> commit?
> >>
> >>Thanks,
> >>Tina
> >>
> >>> -----Original Message-----
> >>> From: Mike Tutkowski
> >>>[mailto:mike.tutkowski@solidfire.com<mailto:mike.tutkowski@solidfire.
> >>>com
> >>>>]
> >>> Sent: 07 April 2014 7:53 AM
> >>> To: dev@cloudstack.apache.org<ma...@cloudstack.apache.org>
> >>> Subject: Re: [4.4] Current State
> >>>
> >>> XS 6.1
> >>>
> >>> On Monday, April 7, 2014, Murali Reddy
> >>><Mu...@citrix.com>> wrote:
> >>>
> >>> >
> >>> > Are you running XS 6.2? Have not tried latest 4.4, but last week
> >>> > with plain XenServer 6.2 I am running into several xapi errors
> >>> > after the commit
> >>> > 1439c69b7e4396d0b8b26076585c6465e44624f3 to remove XAPI jar.
> >>> >
> >>> > I able to run 4.4 with XenServer 6.2 fine with the previous commit
> >>> > 3ee55cd17b941b1fdb1e0bb150bebfb8ece8155d though.
> >>> >
> >>> > On 07/04/14 11:47 AM, "Mike Tutkowski"
> >>> >
> >>><mi...@solidfire.com><
> ja
> >>>vas
> >>>cript:;>
> >>> > >
> >>> > wrote:
> >>> >
> >>> > >Hi,
> >>> > >
> >>> > >Sorry for all the e-mails today. I must have spent 6 hours (to no
> >>> > >avail) trying to get 4.4 into a usable state with XenServer or
> >>> > >VMware so that I could demo a 4.4 feature for a customer tomorrow.
> >>> > >
> >>> > >Is anyone else experiencing massive issues getting a cloud up and
> >>> > >running with current 4.4?
> >>> > >
> >>> > >Perhaps it's my imagination, but it seems for being past feature
> >>> > >freeze that the code should be a lot more reliable.
> >>> > >
> >>> > >Thoughts?
> >>> > >
> >>> > >Thanks
> >>> > >
> >>> > >--
> >>> > >*Mike Tutkowski*
> >>> > >*Senior CloudStack Developer, SolidFire Inc.*
> >>> > >e:
> >>>mike.tutkowski@solidfire.com<ma...@solidfire.com>
> >>><javascript:;>
> >>> > >o: 303.746.7302<tel:303.746.7302> Advancing the way the world
> >>> > >uses the
> >>> > >cloud<http://solidfire.com/solution/overview/?video=play>
> >>> > >*(tm)*
> >>> > >
> >>> >
> >>> >
> >>> >
> >>>
> >>> --
> >>> *Mike Tutkowski*
> >>> *Senior CloudStack Developer, SolidFire Inc.*
> >>> e: mike.tutkowski@solidfire.com<ma...@solidfire.com>
> >>> o: 303.746.7302<tel:303.746.7302>
> >>> Advancing the way the world uses the
> >>> cloud<http://solidfire.com/solution/overview/?video=play>
> >>> *(tm)*
> >>
> >
> >
> >
> >
> >--
> >Mike Tutkowski
> >Senior CloudStack Developer, SolidFire Inc.
> >e: mike.tutkowski@solidfire.com<ma...@solidfire.com>
> >o: 303.746.7302
> >Advancing the way the world uses the
> >cloud<http://solidfire.com/solution/overview/?video=play>(tm)
> >
>
Re: [4.4] Current State
Posted by Mike Tutkowski <mi...@solidfire.com>.
I'm personally a bit concerned about changes of this nature being put in
post feature freeze. I know it sounds like a fairly easy change, but the
ramifications can be huge.
However, being that I'm at ApacheCon and the CCC this week (and not doing
much CS development), this won't be personally blocking me until the
weekend.
For the demo that I was planning to use 4.4, I can use 4.3.
What do others think? How impactful has this been to people?
On Mon, Apr 7, 2014 at 10:15 AM, David Nalley <da...@gnsa.us> wrote:
> In the meantime (assuming this will take you more than a few hours)
> should we revert?
>
> --David
>
> On Mon, Apr 7, 2014 at 10:42 AM, Konstantina Chremmou
> <ko...@citrix.com> wrote:
> > It seems to me the problem is the xmlrpc dependency of the XAPI jar
> rather than the jar itself, as the changes between the previous version and
> the latest one do not explain this sort of errors. The jar we ship depends
> on 3.1 while cloudstack was using 3.1.3 which contains several bug fixes
> compared to the old one. What I can do is upload a new jar with corrected
> dependency and submit a new patch.
> >
> >
> > From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
> > Sent: 07 April 2014 3:06 PM
> > To: dev@cloudstack.apache.org
> > Cc: Konstantina Chremmou
> > Subject: Re: [4.4] Current State
> >
> > Now that I think about it, the issue I sent an e-mail regarding earlier
> where I could not create an SR (SR.create) only started happening after the
> XAPI change.
> >
> > Due to this issue, managed storage is currently not functional with
> XenServer, which is blocking my 4.4 testing.
> >
> > On Mon, Apr 7, 2014 at 5:44 AM, Murali Reddy <Murali.Reddy@citrix.com
> <ma...@citrix.com>> wrote:
> > Errors I have seen are similar to log's pasted by Sanjay. I am running
> > into below error while stopping and starting the VM's.
> >
> > 2014-04-07 13:26:38,960 DEBUG [c.c.h.x.r.CitrixResourceBase]
> > (DirectAgent-107:ctx-0aa97361) cannot get host enabled status, host
> > 10.147.28.60 due to org.apache.xmlrpc.client.XmlRpcClientException:
> Failed
> > to parse servers response: Premature end of file.
> > org.apache.xmlrpc.client.XmlRpcClientException: Failed to parse servers
> > response: Premature end of file.
> > at
> >
> org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcStreamTra
> > nsport.java:177)
> > at
> >
> org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(XmlRpcStreamTran
> > sport.java:145)
> > at
> >
> org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest(XmlRpcHttpTranspor
> > t.java:94)
> > at
> >
> org.apache.xmlrpc.client.XmlRpcSunHttpTransport.sendRequest(XmlRpcSunHttpTr
> > ansport.java:44)
> > at
> >
> org.apache.xmlrpc.client.XmlRpcClientWorker.execute(XmlRpcClientWorker.java
> > :53)
> > at
> org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:166)
> > at
> org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:136)
> > at
> org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:125)
> > at com.xensource.xenapi.Connection.dispatch(Connection.java:330)
> > at
> >
> com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnecti
> > on.dispatch(XenServerConnectionPool.java:457)
> > at com.xensource.xenapi.Host.getEnabled(Host.java:672)
> > at
> >
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.pingXAPI(CitrixResourc
> > eBase.java:409)
> > at
> >
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.getCurrentStatus(Citri
> > xResourceBase.java:4302)
> > at
> >
> com.cloud.agent.manager.DirectAgentAttache$PingTask.runInContext(DirectAgen
> > tAttache.java:144)
> > at
> >
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedC
> > ontextRunnable.java:49)
> > at
> >
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(Def
> > aultManagedContext.java:56)
> > at
> >
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithCo
> > ntext(DefaultManagedContext.java:103)
> > at
> >
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithCon
> > text(DefaultManagedContext.java:53)
> > at
> >
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedCon
> > textRunnable.java:46)
> > at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> > at
> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
> > at
> >
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access
> > $301(ScheduledThreadPoolExecutor.java:178)
> > at
> >
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Sc
> > heduledThreadPoolExecutor.java:293)
> > at
> >
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1
> > 145)
> > at
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:
> > 615)
> > at java.lang.Thread.run(Thread.java:744)
> > Caused by: org.xml.sax.SAXParseException; Premature end of file.
> > at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
> Source)
> > at
> >
> org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcStreamTra
> > nsport.java:175)
> >
> >
> >
> > On 07/04/14 4:51 PM, "Sanjay Tripathi" <sanjay.tripathi@citrix.com
> <ma...@citrix.com>> wrote:
> >
> >>Hi Tina,
> >>
> >>Even I am facing similar issues after the change in XAPI. A lot of
> >>exceptions are coming when CS tries to launch system VMs.
> >>
> >>Please find the management server logs at: http://pastebin.com/6s44hDq5.
> >>
> >>--Sanjay
> >>
> >>-----Original Message-----
> >>From: Konstantina Chremmou [mailto:konstantina.chremmou@citrix.com
> <ma...@citrix.com>]
> >>Sent: Monday, April 7, 2014 4:21 PM
> >>To: dev@cloudstack.apache.org<ma...@cloudstack.apache.org>
> >>Subject: RE: [4.4] Current State
> >>
> >>Hi Murali,
> >>
> >>The latest XAPI jar can be used with older versions of xenserver. Could
> >>you please specify what are the exact errors you get after that commit?
> >>
> >>Thanks,
> >>Tina
> >>
> >>> -----Original Message-----
> >>> From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com<mailto:
> mike.tutkowski@solidfire.com>]
> >>> Sent: 07 April 2014 7:53 AM
> >>> To: dev@cloudstack.apache.org<ma...@cloudstack.apache.org>
> >>> Subject: Re: [4.4] Current State
> >>>
> >>> XS 6.1
> >>>
> >>> On Monday, April 7, 2014, Murali Reddy <Murali.Reddy@citrix.com
> <ma...@citrix.com>> wrote:
> >>>
> >>> >
> >>> > Are you running XS 6.2? Have not tried latest 4.4, but last week
> >>> > with plain XenServer 6.2 I am running into several xapi errors after
> >>> > the commit
> >>> > 1439c69b7e4396d0b8b26076585c6465e44624f3 to remove XAPI jar.
> >>> >
> >>> > I able to run 4.4 with XenServer 6.2 fine with the previous commit
> >>> > 3ee55cd17b941b1fdb1e0bb150bebfb8ece8155d though.
> >>> >
> >>> > On 07/04/14 11:47 AM, "Mike Tutkowski"
> >>> > <mike.tutkowski@solidfire.com<mailto:mike.tutkowski@solidfire.com
> ><javascript:;>
> >>> > >
> >>> > wrote:
> >>> >
> >>> > >Hi,
> >>> > >
> >>> > >Sorry for all the e-mails today. I must have spent 6 hours (to no
> >>> > >avail) trying to get 4.4 into a usable state with XenServer or
> >>> > >VMware so that I could demo a 4.4 feature for a customer tomorrow.
> >>> > >
> >>> > >Is anyone else experiencing massive issues getting a cloud up and
> >>> > >running with current 4.4?
> >>> > >
> >>> > >Perhaps it's my imagination, but it seems for being past feature
> >>> > >freeze that the code should be a lot more reliable.
> >>> > >
> >>> > >Thoughts?
> >>> > >
> >>> > >Thanks
> >>> > >
> >>> > >--
> >>> > >*Mike Tutkowski*
> >>> > >*Senior CloudStack Developer, SolidFire Inc.*
> >>> > >e: mike.tutkowski@solidfire.com<ma...@solidfire.com>
> <javascript:;>
> >>> > >o: 303.746.7302<tel:303.746.7302>
> >>> > >Advancing the way the world uses the
> >>> > >cloud<http://solidfire.com/solution/overview/?video=play>
> >>> > >*(tm)*
> >>> > >
> >>> >
> >>> >
> >>> >
> >>>
> >>> --
> >>> *Mike Tutkowski*
> >>> *Senior CloudStack Developer, SolidFire Inc.*
> >>> e: mike.tutkowski@solidfire.com<ma...@solidfire.com>
> >>> o: 303.746.7302<tel:303.746.7302>
> >>> Advancing the way the world uses the
> >>> cloud<http://solidfire.com/solution/overview/?video=play>
> >>> *(tm)*
> >>
> >
> >
> >
> >
> > --
> > Mike Tutkowski
> > Senior CloudStack Developer, SolidFire Inc.
> > e: mike.tutkowski@solidfire.com<ma...@solidfire.com>
> > o: 303.746.7302
> > Advancing the way the world uses the cloud<
> http://solidfire.com/solution/overview/?video=play>(tm)
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*
Re: [4.4] Current State
Posted by David Nalley <da...@gnsa.us>.
In the meantime (assuming this will take you more than a few hours)
should we revert?
--David
On Mon, Apr 7, 2014 at 10:42 AM, Konstantina Chremmou
<ko...@citrix.com> wrote:
> It seems to me the problem is the xmlrpc dependency of the XAPI jar rather than the jar itself, as the changes between the previous version and the latest one do not explain this sort of errors. The jar we ship depends on 3.1 while cloudstack was using 3.1.3 which contains several bug fixes compared to the old one. What I can do is upload a new jar with corrected dependency and submit a new patch.
>
>
> From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
> Sent: 07 April 2014 3:06 PM
> To: dev@cloudstack.apache.org
> Cc: Konstantina Chremmou
> Subject: Re: [4.4] Current State
>
> Now that I think about it, the issue I sent an e-mail regarding earlier where I could not create an SR (SR.create) only started happening after the XAPI change.
>
> Due to this issue, managed storage is currently not functional with XenServer, which is blocking my 4.4 testing.
>
> On Mon, Apr 7, 2014 at 5:44 AM, Murali Reddy <Mu...@citrix.com>> wrote:
> Errors I have seen are similar to log's pasted by Sanjay. I am running
> into below error while stopping and starting the VM's.
>
> 2014-04-07 13:26:38,960 DEBUG [c.c.h.x.r.CitrixResourceBase]
> (DirectAgent-107:ctx-0aa97361) cannot get host enabled status, host
> 10.147.28.60 due to org.apache.xmlrpc.client.XmlRpcClientException: Failed
> to parse servers response: Premature end of file.
> org.apache.xmlrpc.client.XmlRpcClientException: Failed to parse servers
> response: Premature end of file.
> at
> org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcStreamTra
> nsport.java:177)
> at
> org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(XmlRpcStreamTran
> sport.java:145)
> at
> org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest(XmlRpcHttpTranspor
> t.java:94)
> at
> org.apache.xmlrpc.client.XmlRpcSunHttpTransport.sendRequest(XmlRpcSunHttpTr
> ansport.java:44)
> at
> org.apache.xmlrpc.client.XmlRpcClientWorker.execute(XmlRpcClientWorker.java
> :53)
> at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:166)
> at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:136)
> at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:125)
> at com.xensource.xenapi.Connection.dispatch(Connection.java:330)
> at
> com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnecti
> on.dispatch(XenServerConnectionPool.java:457)
> at com.xensource.xenapi.Host.getEnabled(Host.java:672)
> at
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.pingXAPI(CitrixResourc
> eBase.java:409)
> at
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.getCurrentStatus(Citri
> xResourceBase.java:4302)
> at
> com.cloud.agent.manager.DirectAgentAttache$PingTask.runInContext(DirectAgen
> tAttache.java:144)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedC
> ontextRunnable.java:49)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(Def
> aultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithCo
> ntext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithCon
> text(DefaultManagedContext.java:53)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedCon
> textRunnable.java:46)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access
> $301(ScheduledThreadPoolExecutor.java:178)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Sc
> heduledThreadPoolExecutor.java:293)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1
> 145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:
> 615)
> at java.lang.Thread.run(Thread.java:744)
> Caused by: org.xml.sax.SAXParseException; Premature end of file.
> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
> at
> org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcStreamTra
> nsport.java:175)
>
>
>
> On 07/04/14 4:51 PM, "Sanjay Tripathi" <sa...@citrix.com>> wrote:
>
>>Hi Tina,
>>
>>Even I am facing similar issues after the change in XAPI. A lot of
>>exceptions are coming when CS tries to launch system VMs.
>>
>>Please find the management server logs at: http://pastebin.com/6s44hDq5.
>>
>>--Sanjay
>>
>>-----Original Message-----
>>From: Konstantina Chremmou [mailto:konstantina.chremmou@citrix.com<ma...@citrix.com>]
>>Sent: Monday, April 7, 2014 4:21 PM
>>To: dev@cloudstack.apache.org<ma...@cloudstack.apache.org>
>>Subject: RE: [4.4] Current State
>>
>>Hi Murali,
>>
>>The latest XAPI jar can be used with older versions of xenserver. Could
>>you please specify what are the exact errors you get after that commit?
>>
>>Thanks,
>>Tina
>>
>>> -----Original Message-----
>>> From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com<ma...@solidfire.com>]
>>> Sent: 07 April 2014 7:53 AM
>>> To: dev@cloudstack.apache.org<ma...@cloudstack.apache.org>
>>> Subject: Re: [4.4] Current State
>>>
>>> XS 6.1
>>>
>>> On Monday, April 7, 2014, Murali Reddy <Mu...@citrix.com>> wrote:
>>>
>>> >
>>> > Are you running XS 6.2? Have not tried latest 4.4, but last week
>>> > with plain XenServer 6.2 I am running into several xapi errors after
>>> > the commit
>>> > 1439c69b7e4396d0b8b26076585c6465e44624f3 to remove XAPI jar.
>>> >
>>> > I able to run 4.4 with XenServer 6.2 fine with the previous commit
>>> > 3ee55cd17b941b1fdb1e0bb150bebfb8ece8155d though.
>>> >
>>> > On 07/04/14 11:47 AM, "Mike Tutkowski"
>>> > <mi...@solidfire.com><javascript:;>
>>> > >
>>> > wrote:
>>> >
>>> > >Hi,
>>> > >
>>> > >Sorry for all the e-mails today. I must have spent 6 hours (to no
>>> > >avail) trying to get 4.4 into a usable state with XenServer or
>>> > >VMware so that I could demo a 4.4 feature for a customer tomorrow.
>>> > >
>>> > >Is anyone else experiencing massive issues getting a cloud up and
>>> > >running with current 4.4?
>>> > >
>>> > >Perhaps it's my imagination, but it seems for being past feature
>>> > >freeze that the code should be a lot more reliable.
>>> > >
>>> > >Thoughts?
>>> > >
>>> > >Thanks
>>> > >
>>> > >--
>>> > >*Mike Tutkowski*
>>> > >*Senior CloudStack Developer, SolidFire Inc.*
>>> > >e: mike.tutkowski@solidfire.com<ma...@solidfire.com> <javascript:;>
>>> > >o: 303.746.7302<tel:303.746.7302>
>>> > >Advancing the way the world uses the
>>> > >cloud<http://solidfire.com/solution/overview/?video=play>
>>> > >*(tm)*
>>> > >
>>> >
>>> >
>>> >
>>>
>>> --
>>> *Mike Tutkowski*
>>> *Senior CloudStack Developer, SolidFire Inc.*
>>> e: mike.tutkowski@solidfire.com<ma...@solidfire.com>
>>> o: 303.746.7302<tel:303.746.7302>
>>> Advancing the way the world uses the
>>> cloud<http://solidfire.com/solution/overview/?video=play>
>>> *(tm)*
>>
>
>
>
>
> --
> Mike Tutkowski
> Senior CloudStack Developer, SolidFire Inc.
> e: mike.tutkowski@solidfire.com<ma...@solidfire.com>
> o: 303.746.7302
> Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play>(tm)
Re: [4.4] Current State
Posted by Murali Reddy <Mu...@citrix.com>.
Is there a workaround? I am blocked on testing 4.4 work.
On 07/04/14 8:12 PM, "Konstantina Chremmou"
<ko...@citrix.com> wrote:
>It seems to me the problem is the xmlrpc dependency of the XAPI jar
>rather than the jar itself, as the changes between the previous version
>and the latest one do not explain this sort of errors. The jar we ship
>depends on 3.1 while cloudstack was using 3.1.3 which contains several
>bug fixes compared to the old one. What I can do is upload a new jar with
>corrected dependency and submit a new patch.
>
>
>From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
>Sent: 07 April 2014 3:06 PM
>To: dev@cloudstack.apache.org
>Cc: Konstantina Chremmou
>Subject: Re: [4.4] Current State
>
>Now that I think about it, the issue I sent an e-mail regarding earlier
>where I could not create an SR (SR.create) only started happening after
>the XAPI change.
>
>Due to this issue, managed storage is currently not functional with
>XenServer, which is blocking my 4.4 testing.
>
>On Mon, Apr 7, 2014 at 5:44 AM, Murali Reddy
><Mu...@citrix.com>> wrote:
>Errors I have seen are similar to log's pasted by Sanjay. I am running
>into below error while stopping and starting the VM's.
>
>2014-04-07 13:26:38,960 DEBUG [c.c.h.x.r.CitrixResourceBase]
>(DirectAgent-107:ctx-0aa97361) cannot get host enabled status, host
>10.147.28.60 due to org.apache.xmlrpc.client.XmlRpcClientException: Failed
>to parse servers response: Premature end of file.
>org.apache.xmlrpc.client.XmlRpcClientException: Failed to parse servers
>response: Premature end of file.
> at
>org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcStreamTr
>a
>nsport.java:177)
> at
>org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(XmlRpcStreamTra
>n
>sport.java:145)
> at
>org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest(XmlRpcHttpTranspo
>r
>t.java:94)
> at
>org.apache.xmlrpc.client.XmlRpcSunHttpTransport.sendRequest(XmlRpcSunHttpT
>r
>ansport.java:44)
> at
>org.apache.xmlrpc.client.XmlRpcClientWorker.execute(XmlRpcClientWorker.jav
>a
>:53)
> at
>org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:166)
> at
>org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:136)
> at
>org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:125)
> at com.xensource.xenapi.Connection.dispatch(Connection.java:330)
> at
>com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnect
>i
>on.dispatch(XenServerConnectionPool.java:457)
> at com.xensource.xenapi.Host.getEnabled(Host.java:672)
> at
>com.cloud.hypervisor.xen.resource.CitrixResourceBase.pingXAPI(CitrixResour
>c
>eBase.java:409)
> at
>com.cloud.hypervisor.xen.resource.CitrixResourceBase.getCurrentStatus(Citr
>i
>xResourceBase.java:4302)
> at
>com.cloud.agent.manager.DirectAgentAttache$PingTask.runInContext(DirectAge
>n
>tAttache.java:144)
> at
>org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(Managed
>C
>ontextRunnable.java:49)
> at
>org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(De
>f
>aultManagedContext.java:56)
> at
>org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithC
>o
>ntext(DefaultManagedContext.java:103)
> at
>org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithCo
>n
>text(DefaultManagedContext.java:53)
> at
>org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedCo
>n
>textRunnable.java:46)
> at
>java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at
>java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
> at
>java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.acces
>s
>$301(ScheduledThreadPoolExecutor.java:178)
> at
>java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(S
>c
>heduledThreadPoolExecutor.java:293)
> at
>java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:
>1
>145)
> at
>java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java
>:
>615)
> at java.lang.Thread.run(Thread.java:744)
>Caused by: org.xml.sax.SAXParseException; Premature end of file.
> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
>Source)
> at
>org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcStreamTr
>a
>nsport.java:175)
>
>
>
>On 07/04/14 4:51 PM, "Sanjay Tripathi"
><sa...@citrix.com>> wrote:
>
>>Hi Tina,
>>
>>Even I am facing similar issues after the change in XAPI. A lot of
>>exceptions are coming when CS tries to launch system VMs.
>>
>>Please find the management server logs at: http://pastebin.com/6s44hDq5.
>>
>>--Sanjay
>>
>>-----Original Message-----
>>From: Konstantina Chremmou
>>[mailto:konstantina.chremmou@citrix.com<mailto:konstantina.chremmou@citri
>>x.com>]
>>Sent: Monday, April 7, 2014 4:21 PM
>>To: dev@cloudstack.apache.org<ma...@cloudstack.apache.org>
>>Subject: RE: [4.4] Current State
>>
>>Hi Murali,
>>
>>The latest XAPI jar can be used with older versions of xenserver. Could
>>you please specify what are the exact errors you get after that commit?
>>
>>Thanks,
>>Tina
>>
>>> -----Original Message-----
>>> From: Mike Tutkowski
>>>[mailto:mike.tutkowski@solidfire.com<mailto:mike.tutkowski@solidfire.com
>>>>]
>>> Sent: 07 April 2014 7:53 AM
>>> To: dev@cloudstack.apache.org<ma...@cloudstack.apache.org>
>>> Subject: Re: [4.4] Current State
>>>
>>> XS 6.1
>>>
>>> On Monday, April 7, 2014, Murali Reddy
>>><Mu...@citrix.com>> wrote:
>>>
>>> >
>>> > Are you running XS 6.2? Have not tried latest 4.4, but last week
>>> > with plain XenServer 6.2 I am running into several xapi errors after
>>> > the commit
>>> > 1439c69b7e4396d0b8b26076585c6465e44624f3 to remove XAPI jar.
>>> >
>>> > I able to run 4.4 with XenServer 6.2 fine with the previous commit
>>> > 3ee55cd17b941b1fdb1e0bb150bebfb8ece8155d though.
>>> >
>>> > On 07/04/14 11:47 AM, "Mike Tutkowski"
>>> >
>>><mi...@solidfire.com><javas
>>>cript:;>
>>> > >
>>> > wrote:
>>> >
>>> > >Hi,
>>> > >
>>> > >Sorry for all the e-mails today. I must have spent 6 hours (to no
>>> > >avail) trying to get 4.4 into a usable state with XenServer or
>>> > >VMware so that I could demo a 4.4 feature for a customer tomorrow.
>>> > >
>>> > >Is anyone else experiencing massive issues getting a cloud up and
>>> > >running with current 4.4?
>>> > >
>>> > >Perhaps it's my imagination, but it seems for being past feature
>>> > >freeze that the code should be a lot more reliable.
>>> > >
>>> > >Thoughts?
>>> > >
>>> > >Thanks
>>> > >
>>> > >--
>>> > >*Mike Tutkowski*
>>> > >*Senior CloudStack Developer, SolidFire Inc.*
>>> > >e:
>>>mike.tutkowski@solidfire.com<ma...@solidfire.com>
>>><javascript:;>
>>> > >o: 303.746.7302<tel:303.746.7302>
>>> > >Advancing the way the world uses the
>>> > >cloud<http://solidfire.com/solution/overview/?video=play>
>>> > >*(tm)*
>>> > >
>>> >
>>> >
>>> >
>>>
>>> --
>>> *Mike Tutkowski*
>>> *Senior CloudStack Developer, SolidFire Inc.*
>>> e: mike.tutkowski@solidfire.com<ma...@solidfire.com>
>>> o: 303.746.7302<tel:303.746.7302>
>>> Advancing the way the world uses the
>>> cloud<http://solidfire.com/solution/overview/?video=play>
>>> *(tm)*
>>
>
>
>
>
>--
>Mike Tutkowski
>Senior CloudStack Developer, SolidFire Inc.
>e: mike.tutkowski@solidfire.com<ma...@solidfire.com>
>o: 303.746.7302
>Advancing the way the world uses the
>cloud<http://solidfire.com/solution/overview/?video=play>(tm)
>
RE: [4.4] Current State
Posted by Konstantina Chremmou <ko...@citrix.com>.
It seems to me the problem is the xmlrpc dependency of the XAPI jar rather than the jar itself, as the changes between the previous version and the latest one do not explain this sort of errors. The jar we ship depends on 3.1 while cloudstack was using 3.1.3 which contains several bug fixes compared to the old one. What I can do is upload a new jar with corrected dependency and submit a new patch.
From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
Sent: 07 April 2014 3:06 PM
To: dev@cloudstack.apache.org
Cc: Konstantina Chremmou
Subject: Re: [4.4] Current State
Now that I think about it, the issue I sent an e-mail regarding earlier where I could not create an SR (SR.create) only started happening after the XAPI change.
Due to this issue, managed storage is currently not functional with XenServer, which is blocking my 4.4 testing.
On Mon, Apr 7, 2014 at 5:44 AM, Murali Reddy <Mu...@citrix.com>> wrote:
Errors I have seen are similar to log's pasted by Sanjay. I am running
into below error while stopping and starting the VM's.
2014-04-07 13:26:38,960 DEBUG [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-107:ctx-0aa97361) cannot get host enabled status, host
10.147.28.60 due to org.apache.xmlrpc.client.XmlRpcClientException: Failed
to parse servers response: Premature end of file.
org.apache.xmlrpc.client.XmlRpcClientException: Failed to parse servers
response: Premature end of file.
at
org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcStreamTra
nsport.java:177)
at
org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(XmlRpcStreamTran
sport.java:145)
at
org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest(XmlRpcHttpTranspor
t.java:94)
at
org.apache.xmlrpc.client.XmlRpcSunHttpTransport.sendRequest(XmlRpcSunHttpTr
ansport.java:44)
at
org.apache.xmlrpc.client.XmlRpcClientWorker.execute(XmlRpcClientWorker.java
:53)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:166)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:136)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:125)
at com.xensource.xenapi.Connection.dispatch(Connection.java:330)
at
com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnecti
on.dispatch(XenServerConnectionPool.java:457)
at com.xensource.xenapi.Host.getEnabled(Host.java:672)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.pingXAPI(CitrixResourc
eBase.java:409)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.getCurrentStatus(Citri
xResourceBase.java:4302)
at
com.cloud.agent.manager.DirectAgentAttache$PingTask.runInContext(DirectAgen
tAttache.java:144)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedC
ontextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(Def
aultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithCo
ntext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithCon
text(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedCon
textRunnable.java:46)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access
$301(ScheduledThreadPoolExecutor.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Sc
heduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1
145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:
615)
at java.lang.Thread.run(Thread.java:744)
Caused by: org.xml.sax.SAXParseException; Premature end of file.
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at
org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcStreamTra
nsport.java:175)
On 07/04/14 4:51 PM, "Sanjay Tripathi" <sa...@citrix.com>> wrote:
>Hi Tina,
>
>Even I am facing similar issues after the change in XAPI. A lot of
>exceptions are coming when CS tries to launch system VMs.
>
>Please find the management server logs at: http://pastebin.com/6s44hDq5.
>
>--Sanjay
>
>-----Original Message-----
>From: Konstantina Chremmou [mailto:konstantina.chremmou@citrix.com<ma...@citrix.com>]
>Sent: Monday, April 7, 2014 4:21 PM
>To: dev@cloudstack.apache.org<ma...@cloudstack.apache.org>
>Subject: RE: [4.4] Current State
>
>Hi Murali,
>
>The latest XAPI jar can be used with older versions of xenserver. Could
>you please specify what are the exact errors you get after that commit?
>
>Thanks,
>Tina
>
>> -----Original Message-----
>> From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com<ma...@solidfire.com>]
>> Sent: 07 April 2014 7:53 AM
>> To: dev@cloudstack.apache.org<ma...@cloudstack.apache.org>
>> Subject: Re: [4.4] Current State
>>
>> XS 6.1
>>
>> On Monday, April 7, 2014, Murali Reddy <Mu...@citrix.com>> wrote:
>>
>> >
>> > Are you running XS 6.2? Have not tried latest 4.4, but last week
>> > with plain XenServer 6.2 I am running into several xapi errors after
>> > the commit
>> > 1439c69b7e4396d0b8b26076585c6465e44624f3 to remove XAPI jar.
>> >
>> > I able to run 4.4 with XenServer 6.2 fine with the previous commit
>> > 3ee55cd17b941b1fdb1e0bb150bebfb8ece8155d though.
>> >
>> > On 07/04/14 11:47 AM, "Mike Tutkowski"
>> > <mi...@solidfire.com><javascript:;>
>> > >
>> > wrote:
>> >
>> > >Hi,
>> > >
>> > >Sorry for all the e-mails today. I must have spent 6 hours (to no
>> > >avail) trying to get 4.4 into a usable state with XenServer or
>> > >VMware so that I could demo a 4.4 feature for a customer tomorrow.
>> > >
>> > >Is anyone else experiencing massive issues getting a cloud up and
>> > >running with current 4.4?
>> > >
>> > >Perhaps it's my imagination, but it seems for being past feature
>> > >freeze that the code should be a lot more reliable.
>> > >
>> > >Thoughts?
>> > >
>> > >Thanks
>> > >
>> > >--
>> > >*Mike Tutkowski*
>> > >*Senior CloudStack Developer, SolidFire Inc.*
>> > >e: mike.tutkowski@solidfire.com<ma...@solidfire.com> <javascript:;>
>> > >o: 303.746.7302<tel:303.746.7302>
>> > >Advancing the way the world uses the
>> > >cloud<http://solidfire.com/solution/overview/?video=play>
>> > >*(tm)*
>> > >
>> >
>> >
>> >
>>
>> --
>> *Mike Tutkowski*
>> *Senior CloudStack Developer, SolidFire Inc.*
>> e: mike.tutkowski@solidfire.com<ma...@solidfire.com>
>> o: 303.746.7302<tel:303.746.7302>
>> Advancing the way the world uses the
>> cloud<http://solidfire.com/solution/overview/?video=play>
>> *(tm)*
>
--
Mike Tutkowski
Senior CloudStack Developer, SolidFire Inc.
e: mike.tutkowski@solidfire.com<ma...@solidfire.com>
o: 303.746.7302
Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play>(tm)
Re: [4.4] Current State
Posted by Mike Tutkowski <mi...@solidfire.com>.
Now that I think about it, the issue I sent an e-mail regarding earlier
where I could not create an SR (SR.create) only started happening after the
XAPI change.
Due to this issue, managed storage is currently not functional with
XenServer, which is blocking my 4.4 testing.
On Mon, Apr 7, 2014 at 5:44 AM, Murali Reddy <Mu...@citrix.com>wrote:
> Errors I have seen are similar to log's pasted by Sanjay. I am running
> into below error while stopping and starting the VM's.
>
> 2014-04-07 13:26:38,960 DEBUG [c.c.h.x.r.CitrixResourceBase]
> (DirectAgent-107:ctx-0aa97361) cannot get host enabled status, host
> 10.147.28.60 due to org.apache.xmlrpc.client.XmlRpcClientException: Failed
> to parse servers response: Premature end of file.
> org.apache.xmlrpc.client.XmlRpcClientException: Failed to parse servers
> response: Premature end of file.
> at
> org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcStreamTra
> nsport.java:177)
> at
> org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(XmlRpcStreamTran
> sport.java:145)
> at
> org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest(XmlRpcHttpTranspor
> t.java:94)
> at
> org.apache.xmlrpc.client.XmlRpcSunHttpTransport.sendRequest(XmlRpcSunHttpTr
> ansport.java:44)
> at
> org.apache.xmlrpc.client.XmlRpcClientWorker.execute(XmlRpcClientWorker.java
> :53)
> at
> org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:166)
> at
> org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:136)
> at
> org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:125)
> at com.xensource.xenapi.Connection.dispatch(Connection.java:330)
> at
> com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnecti
> on.dispatch(XenServerConnectionPool.java:457)
> at com.xensource.xenapi.Host.getEnabled(Host.java:672)
> at
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.pingXAPI(CitrixResourc
> eBase.java:409)
> at
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.getCurrentStatus(Citri
> xResourceBase.java:4302)
> at
> com.cloud.agent.manager.DirectAgentAttache$PingTask.runInContext(DirectAgen
> tAttache.java:144)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedC
> ontextRunnable.java:49)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(Def
> aultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithCo
> ntext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithCon
> text(DefaultManagedContext.java:53)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedCon
> textRunnable.java:46)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access
> $301(ScheduledThreadPoolExecutor.java:178)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Sc
> heduledThreadPoolExecutor.java:293)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1
> 145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:
> 615)
> at java.lang.Thread.run(Thread.java:744)
> Caused by: org.xml.sax.SAXParseException; Premature end of file.
> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
> Source)
> at
> org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcStreamTra
> nsport.java:175)
>
>
>
> On 07/04/14 4:51 PM, "Sanjay Tripathi" <sa...@citrix.com> wrote:
>
> >Hi Tina,
> >
> >Even I am facing similar issues after the change in XAPI. A lot of
> >exceptions are coming when CS tries to launch system VMs.
> >
> >Please find the management server logs at: http://pastebin.com/6s44hDq5.
> >
> >--Sanjay
> >
> >-----Original Message-----
> >From: Konstantina Chremmou [mailto:konstantina.chremmou@citrix.com]
> >Sent: Monday, April 7, 2014 4:21 PM
> >To: dev@cloudstack.apache.org
> >Subject: RE: [4.4] Current State
> >
> >Hi Murali,
> >
> >The latest XAPI jar can be used with older versions of xenserver. Could
> >you please specify what are the exact errors you get after that commit?
> >
> >Thanks,
> >Tina
> >
> >> -----Original Message-----
> >> From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
> >> Sent: 07 April 2014 7:53 AM
> >> To: dev@cloudstack.apache.org
> >> Subject: Re: [4.4] Current State
> >>
> >> XS 6.1
> >>
> >> On Monday, April 7, 2014, Murali Reddy <Mu...@citrix.com> wrote:
> >>
> >> >
> >> > Are you running XS 6.2? Have not tried latest 4.4, but last week
> >> > with plain XenServer 6.2 I am running into several xapi errors after
> >> > the commit
> >> > 1439c69b7e4396d0b8b26076585c6465e44624f3 to remove XAPI jar.
> >> >
> >> > I able to run 4.4 with XenServer 6.2 fine with the previous commit
> >> > 3ee55cd17b941b1fdb1e0bb150bebfb8ece8155d though.
> >> >
> >> > On 07/04/14 11:47 AM, "Mike Tutkowski"
> >> > <mike.tutkowski@solidfire.com<javascript:;>
> >> > >
> >> > wrote:
> >> >
> >> > >Hi,
> >> > >
> >> > >Sorry for all the e-mails today. I must have spent 6 hours (to no
> >> > >avail) trying to get 4.4 into a usable state with XenServer or
> >> > >VMware so that I could demo a 4.4 feature for a customer tomorrow.
> >> > >
> >> > >Is anyone else experiencing massive issues getting a cloud up and
> >> > >running with current 4.4?
> >> > >
> >> > >Perhaps it's my imagination, but it seems for being past feature
> >> > >freeze that the code should be a lot more reliable.
> >> > >
> >> > >Thoughts?
> >> > >
> >> > >Thanks
> >> > >
> >> > >--
> >> > >*Mike Tutkowski*
> >> > >*Senior CloudStack Developer, SolidFire Inc.*
> >> > >e: mike.tutkowski@solidfire.com <javascript:;>
> >> > >o: 303.746.7302
> >> > >Advancing the way the world uses the
> >> > >cloud<http://solidfire.com/solution/overview/?video=play>
> >> > >*(tm)*
> >> > >
> >> >
> >> >
> >> >
> >>
> >> --
> >> *Mike Tutkowski*
> >> *Senior CloudStack Developer, SolidFire Inc.*
> >> e: mike.tutkowski@solidfire.com
> >> o: 303.746.7302
> >> Advancing the way the world uses the
> >> cloud<http://solidfire.com/solution/overview/?video=play>
> >> *(tm)*
> >
>
>
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*
Re: [4.4] Current State
Posted by Murali Reddy <Mu...@citrix.com>.
Errors I have seen are similar to log's pasted by Sanjay. I am running
into below error while stopping and starting the VM's.
2014-04-07 13:26:38,960 DEBUG [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-107:ctx-0aa97361) cannot get host enabled status, host
10.147.28.60 due to org.apache.xmlrpc.client.XmlRpcClientException: Failed
to parse servers response: Premature end of file.
org.apache.xmlrpc.client.XmlRpcClientException: Failed to parse servers
response: Premature end of file.
at
org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcStreamTra
nsport.java:177)
at
org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(XmlRpcStreamTran
sport.java:145)
at
org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest(XmlRpcHttpTranspor
t.java:94)
at
org.apache.xmlrpc.client.XmlRpcSunHttpTransport.sendRequest(XmlRpcSunHttpTr
ansport.java:44)
at
org.apache.xmlrpc.client.XmlRpcClientWorker.execute(XmlRpcClientWorker.java
:53)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:166)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:136)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:125)
at com.xensource.xenapi.Connection.dispatch(Connection.java:330)
at
com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnecti
on.dispatch(XenServerConnectionPool.java:457)
at com.xensource.xenapi.Host.getEnabled(Host.java:672)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.pingXAPI(CitrixResourc
eBase.java:409)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.getCurrentStatus(Citri
xResourceBase.java:4302)
at
com.cloud.agent.manager.DirectAgentAttache$PingTask.runInContext(DirectAgen
tAttache.java:144)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedC
ontextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(Def
aultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithCo
ntext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithCon
text(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedCon
textRunnable.java:46)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access
$301(ScheduledThreadPoolExecutor.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Sc
heduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1
145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:
615)
at java.lang.Thread.run(Thread.java:744)
Caused by: org.xml.sax.SAXParseException; Premature end of file.
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at
org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcStreamTra
nsport.java:175)
On 07/04/14 4:51 PM, "Sanjay Tripathi" <sa...@citrix.com> wrote:
>Hi Tina,
>
>Even I am facing similar issues after the change in XAPI. A lot of
>exceptions are coming when CS tries to launch system VMs.
>
>Please find the management server logs at: http://pastebin.com/6s44hDq5.
>
>--Sanjay
>
>-----Original Message-----
>From: Konstantina Chremmou [mailto:konstantina.chremmou@citrix.com]
>Sent: Monday, April 7, 2014 4:21 PM
>To: dev@cloudstack.apache.org
>Subject: RE: [4.4] Current State
>
>Hi Murali,
>
>The latest XAPI jar can be used with older versions of xenserver. Could
>you please specify what are the exact errors you get after that commit?
>
>Thanks,
>Tina
>
>> -----Original Message-----
>> From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
>> Sent: 07 April 2014 7:53 AM
>> To: dev@cloudstack.apache.org
>> Subject: Re: [4.4] Current State
>>
>> XS 6.1
>>
>> On Monday, April 7, 2014, Murali Reddy <Mu...@citrix.com> wrote:
>>
>> >
>> > Are you running XS 6.2? Have not tried latest 4.4, but last week
>> > with plain XenServer 6.2 I am running into several xapi errors after
>> > the commit
>> > 1439c69b7e4396d0b8b26076585c6465e44624f3 to remove XAPI jar.
>> >
>> > I able to run 4.4 with XenServer 6.2 fine with the previous commit
>> > 3ee55cd17b941b1fdb1e0bb150bebfb8ece8155d though.
>> >
>> > On 07/04/14 11:47 AM, "Mike Tutkowski"
>> > <mike.tutkowski@solidfire.com<javascript:;>
>> > >
>> > wrote:
>> >
>> > >Hi,
>> > >
>> > >Sorry for all the e-mails today. I must have spent 6 hours (to no
>> > >avail) trying to get 4.4 into a usable state with XenServer or
>> > >VMware so that I could demo a 4.4 feature for a customer tomorrow.
>> > >
>> > >Is anyone else experiencing massive issues getting a cloud up and
>> > >running with current 4.4?
>> > >
>> > >Perhaps it's my imagination, but it seems for being past feature
>> > >freeze that the code should be a lot more reliable.
>> > >
>> > >Thoughts?
>> > >
>> > >Thanks
>> > >
>> > >--
>> > >*Mike Tutkowski*
>> > >*Senior CloudStack Developer, SolidFire Inc.*
>> > >e: mike.tutkowski@solidfire.com <javascript:;>
>> > >o: 303.746.7302
>> > >Advancing the way the world uses the
>> > >cloud<http://solidfire.com/solution/overview/?video=play>
>> > >*(tm)*
>> > >
>> >
>> >
>> >
>>
>> --
>> *Mike Tutkowski*
>> *Senior CloudStack Developer, SolidFire Inc.*
>> e: mike.tutkowski@solidfire.com
>> o: 303.746.7302
>> Advancing the way the world uses the
>> cloud<http://solidfire.com/solution/overview/?video=play>
>> *(tm)*
>
RE: [4.4] Current State
Posted by Sanjay Tripathi <sa...@citrix.com>.
Hi Tina,
Even I am facing similar issues after the change in XAPI. A lot of exceptions are coming when CS tries to launch system VMs.
Please find the management server logs at: http://pastebin.com/6s44hDq5.
--Sanjay
-----Original Message-----
From: Konstantina Chremmou [mailto:konstantina.chremmou@citrix.com]
Sent: Monday, April 7, 2014 4:21 PM
To: dev@cloudstack.apache.org
Subject: RE: [4.4] Current State
Hi Murali,
The latest XAPI jar can be used with older versions of xenserver. Could you please specify what are the exact errors you get after that commit?
Thanks,
Tina
> -----Original Message-----
> From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
> Sent: 07 April 2014 7:53 AM
> To: dev@cloudstack.apache.org
> Subject: Re: [4.4] Current State
>
> XS 6.1
>
> On Monday, April 7, 2014, Murali Reddy <Mu...@citrix.com> wrote:
>
> >
> > Are you running XS 6.2? Have not tried latest 4.4, but last week
> > with plain XenServer 6.2 I am running into several xapi errors after
> > the commit
> > 1439c69b7e4396d0b8b26076585c6465e44624f3 to remove XAPI jar.
> >
> > I able to run 4.4 with XenServer 6.2 fine with the previous commit
> > 3ee55cd17b941b1fdb1e0bb150bebfb8ece8155d though.
> >
> > On 07/04/14 11:47 AM, "Mike Tutkowski"
> > <mike.tutkowski@solidfire.com<javascript:;>
> > >
> > wrote:
> >
> > >Hi,
> > >
> > >Sorry for all the e-mails today. I must have spent 6 hours (to no
> > >avail) trying to get 4.4 into a usable state with XenServer or
> > >VMware so that I could demo a 4.4 feature for a customer tomorrow.
> > >
> > >Is anyone else experiencing massive issues getting a cloud up and
> > >running with current 4.4?
> > >
> > >Perhaps it's my imagination, but it seems for being past feature
> > >freeze that the code should be a lot more reliable.
> > >
> > >Thoughts?
> > >
> > >Thanks
> > >
> > >--
> > >*Mike Tutkowski*
> > >*Senior CloudStack Developer, SolidFire Inc.*
> > >e: mike.tutkowski@solidfire.com <javascript:;>
> > >o: 303.746.7302
> > >Advancing the way the world uses the
> > >cloud<http://solidfire.com/solution/overview/?video=play>
> > >*(tm)*
> > >
> >
> >
> >
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud<http://solidfire.com/solution/overview/?video=play>
> *(tm)*
RE: [4.4] Current State
Posted by Konstantina Chremmou <ko...@citrix.com>.
Hi Murali,
The latest XAPI jar can be used with older versions of xenserver. Could you please specify what are the exact errors you get after that commit?
Thanks,
Tina
> -----Original Message-----
> From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
> Sent: 07 April 2014 7:53 AM
> To: dev@cloudstack.apache.org
> Subject: Re: [4.4] Current State
>
> XS 6.1
>
> On Monday, April 7, 2014, Murali Reddy <Mu...@citrix.com> wrote:
>
> >
> > Are you running XS 6.2? Have not tried latest 4.4, but last week with
> > plain XenServer 6.2 I am running into several xapi errors after the
> > commit
> > 1439c69b7e4396d0b8b26076585c6465e44624f3 to remove XAPI jar.
> >
> > I able to run 4.4 with XenServer 6.2 fine with the previous commit
> > 3ee55cd17b941b1fdb1e0bb150bebfb8ece8155d though.
> >
> > On 07/04/14 11:47 AM, "Mike Tutkowski"
> > <mike.tutkowski@solidfire.com<javascript:;>
> > >
> > wrote:
> >
> > >Hi,
> > >
> > >Sorry for all the e-mails today. I must have spent 6 hours (to no
> > >avail) trying to get 4.4 into a usable state with XenServer or VMware
> > >so that I could demo a 4.4 feature for a customer tomorrow.
> > >
> > >Is anyone else experiencing massive issues getting a cloud up and
> > >running with current 4.4?
> > >
> > >Perhaps it's my imagination, but it seems for being past feature
> > >freeze that the code should be a lot more reliable.
> > >
> > >Thoughts?
> > >
> > >Thanks
> > >
> > >--
> > >*Mike Tutkowski*
> > >*Senior CloudStack Developer, SolidFire Inc.*
> > >e: mike.tutkowski@solidfire.com <javascript:;>
> > >o: 303.746.7302
> > >Advancing the way the world uses the
> > >cloud<http://solidfire.com/solution/overview/?video=play>
> > >*(tm)*
> > >
> >
> >
> >
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud<http://solidfire.com/solution/overview/?video=play>
> *(tm)*
Re: [4.4] Current State
Posted by Mike Tutkowski <mi...@solidfire.com>.
XS 6.1
On Monday, April 7, 2014, Murali Reddy <Mu...@citrix.com> wrote:
>
> Are you running XS 6.2? Have not tried latest 4.4, but last week with
> plain XenServer 6.2 I am running into several xapi errors after the commit
> 1439c69b7e4396d0b8b26076585c6465e44624f3 to remove XAPI jar.
>
> I able to run 4.4 with XenServer 6.2 fine with the previous commit
> 3ee55cd17b941b1fdb1e0bb150bebfb8ece8155d though.
>
> On 07/04/14 11:47 AM, "Mike Tutkowski" <mike.tutkowski@solidfire.com<javascript:;>
> >
> wrote:
>
> >Hi,
> >
> >Sorry for all the e-mails today. I must have spent 6 hours (to no avail)
> >trying to get 4.4 into a usable state with XenServer or VMware so that I
> >could demo a 4.4 feature for a customer tomorrow.
> >
> >Is anyone else experiencing massive issues getting a cloud up and running
> >with current 4.4?
> >
> >Perhaps it's my imagination, but it seems for being past feature freeze
> >that the code should be a lot more reliable.
> >
> >Thoughts?
> >
> >Thanks
> >
> >--
> >*Mike Tutkowski*
> >*Senior CloudStack Developer, SolidFire Inc.*
> >e: mike.tutkowski@solidfire.com <javascript:;>
> >o: 303.746.7302
> >Advancing the way the world uses the
> >cloud<http://solidfire.com/solution/overview/?video=play>
> >*(tm)*
> >
>
>
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*
Re: [4.4] Current State
Posted by Murali Reddy <Mu...@citrix.com>.
Are you running XS 6.2? Have not tried latest 4.4, but last week with
plain XenServer 6.2 I am running into several xapi errors after the commit
1439c69b7e4396d0b8b26076585c6465e44624f3 to remove XAPI jar.
I able to run 4.4 with XenServer 6.2 fine with the previous commit
3ee55cd17b941b1fdb1e0bb150bebfb8ece8155d though.
On 07/04/14 11:47 AM, "Mike Tutkowski" <mi...@solidfire.com>
wrote:
>Hi,
>
>Sorry for all the e-mails today. I must have spent 6 hours (to no avail)
>trying to get 4.4 into a usable state with XenServer or VMware so that I
>could demo a 4.4 feature for a customer tomorrow.
>
>Is anyone else experiencing massive issues getting a cloud up and running
>with current 4.4?
>
>Perhaps it's my imagination, but it seems for being past feature freeze
>that the code should be a lot more reliable.
>
>Thoughts?
>
>Thanks
>
>--
>*Mike Tutkowski*
>*Senior CloudStack Developer, SolidFire Inc.*
>e: mike.tutkowski@solidfire.com
>o: 303.746.7302
>Advancing the way the world uses the
>cloud<http://solidfire.com/solution/overview/?video=play>
>*(tm)*
>