On Thu, Feb 28, 2013 at 11:42:12AM +0530, Prasanna Santhanam wrote:
> On Thu, Feb 28, 2013 at 01:47:34AM +0530, Mike Tutkowski wrote:
> > I ran the following:
> >
> > git fetch upstream
> >
> > where upstream equals https://github.com/apache/incubator-cloudstack.git
> This guy ^^ is out of date (
On Thu, Feb 28, 2013 at 01:47:34AM +0530, Mike Tutkowski wrote:
> I ran the following:
>
> git fetch upstream
>
> where upstream equals https://github.com/apache/incubator-cloudstack.git
This guy ^^ is out of date (14d old). Don't use him as upstream. Use
the official repo git-wip-us:// instead a
: Issue in storage_refactor branch
So, being a bit new to Git, let me make sure I did this correctly. :)
I ran the following:
git fetch upstream
where upstream equals https://github.com/apache/incubator-cloudstack.git
No output was printed...I was just returned to the command prompt.
I take it that means
atest.
If that is the case, then I believe this problem does not exist in master
and I can do my development in master.
Sound correct?
On Wed, Feb 27, 2013 at 11:54 AM, Edison Su wrote:
> Hi Mike, cloud you try it on latest master branch? I already merged
> storage_refactor branch into mas
Hi Mike, cloud you try it on latest master branch? I already merged
storage_refactor branch into master already.
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: Wednesday, February 27, 2013 10:44 AM
To: cloudstack-dev@incubator.apache.org; Edison Su
Subject: Issue in
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
at
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
On Wed, Feb 27, 2013 at 11:44 AM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:
> Hi,
>
> I'm currently using the storage_refactor branch
Hi,
I'm currently using the storage_refactor branch and have come across an
issue while trying to create Primary Storage. My iSCSI target is up and
running. I created a Storage Repository for it in XenServer. In
CloudStack, I tried to create Primary Storage (PreSetup type), but ge
The more memory, the better.
> -Original Message-
> From: Jessica Wang
> Sent: Wednesday, February 13, 2013 10:23 AM
> To: cloudstack-dev@incubator.apache.org; Edison Su
> Subject: RE: Can't run Jetty on storage_refactor branch
>
> Edison,
>
> How about
February 12, 2013 3:33 PM
To: cloudstack-dev@incubator.apache.org
Subject: RE: Can't run Jetty on storage_refactor branch
If you are running jetty on maven command line, run the following:
export MAVEN_OPTS="-XX:MaxPermSize=512m -Xmx1024m"
before jetty:run.
> -Origin
Loader.initWebApplicationContext(ContextLoader.java:283)
>>>>> at
>>>>> org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:111)
>>>>> at
>>>>> org.mortbay.jetty.handler.ContextHandler.startCo
;>> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
>>>> at
>>>> org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
>>>> at
>>>> org.mortbay.component.AbstractLifeCycle.start(AbstractL
t; org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecu
ecycleStarter.execute(LifecycleStarter.java:161)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>> at org.apache.maven.cli.Maven
her.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(
gt;> > -Original Message-
>> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>> > Sent: Tuesday, February 12, 2013 1:22 PM
>> > To: cloudstack-dev@incubator.apache.org
>> > Subject: Can't run Jetty on storage_refactor bran
m: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > Sent: Tuesday, February 12, 2013 1:22 PM
> > To: cloudstack-dev@incubator.apache.org
> > Subject: Can't run Jetty on storage_refactor branch
> >
> > Hi,
> >
> > As I indicated in an earlier e-mail,
gt; To: cloudstack-dev@incubator.apache.org
> Subject: Can't run Jetty on storage_refactor branch
>
> Hi,
>
> As I indicated in an earlier e-mail, I have a branch off of the
> storage_refactor
> branch. I can't seem to get Jetty to run on either my branch or on the
>
Hi,
As I indicated in an earlier e-mail, I have a branch off of the
storage_refactor branch. I can't seem to get Jetty to run on either my
branch or on the storage_refactor one, but it works on Master.
Any ideas? It just hangs at that bottom message.
Thanks!
main:
[INFO] Executed tasks
ge-
> > From: Chip Childers [mailto:chip.child...@sungard.com]
> > Sent: Wednesday, February 06, 2013 9:43 PM
> > To: Marcus Sorensen
> > Cc: Mike Tutkowski; Devdeep Singh; cloudstack-dev@incubator.apache.org;
> > Edison Su
> > Subject: Re: storage_refactor br
rensen
> Cc: Mike Tutkowski; Devdeep Singh; cloudstack-dev@incubator.apache.org;
> Edison Su
> Subject: Re: storage_refactor branch
>
> On Wed, Feb 06, 2013 at 10:33:32PM -0700, Marcus Sorensen wrote:
> > On Wed, Feb 6, 2013 at 10:19 PM, Chip Childers
> > wrote:
> >
On Wed, Feb 06, 2013 at 10:33:32PM -0700, Marcus Sorensen wrote:
> On Wed, Feb 6, 2013 at 10:19 PM, Chip Childers
> wrote:
> > On Wed, Feb 06, 2013 at 10:10:27PM -0700, Mike Tutkowski wrote:
> >> OK, thanks...I wasn't sure when feature freeze was.
> >>
> >> Do we have a roadmap that might indicate
On Wed, Feb 6, 2013 at 10:19 PM, Chip Childers
wrote:
> On Wed, Feb 06, 2013 at 10:10:27PM -0700, Mike Tutkowski wrote:
>> OK, thanks...I wasn't sure when feature freeze was.
>>
>> Do we have a roadmap that might indicate when 4.2 (or whatever it will be
>> called) is expected for release?
>
> I s
As you can see, it doesn't matter for you that the storage refactor
branch didn't make it into 4.1, because you wouldn't have had time to
get any storage code into cloudstack 4.1 anyway. So it's fine to
develop in tandem with Edison's branch, so long as it's far enough
along to do so. If he merges
Thanks, Chip!
On Wed, Feb 6, 2013 at 10:19 PM, Chip Childers wrote:
> On Wed, Feb 06, 2013 at 10:10:27PM -0700, Mike Tutkowski wrote:
> > OK, thanks...I wasn't sure when feature freeze was.
> >
> > Do we have a roadmap that might indicate when 4.2 (or whatever it will be
> > called) is expected
On Wed, Feb 06, 2013 at 10:10:27PM -0700, Mike Tutkowski wrote:
> OK, thanks...I wasn't sure when feature freeze was.
>
> Do we have a roadmap that might indicate when 4.2 (or whatever it will be
> called) is expected for release?
I should probaby put this on the wiki, but we've been planning on
ilto:mike.tutkow...@solidfire.com]
> > > Sent: Thursday, February 07, 2013 9:29 AM
> > > To: cloudstack-dev@incubator.apache.org
> > > Cc: Edison Su
> > > Subject: storage_refactor branch
> > >
> > > Hi Edison,
> > >
> > > I ju
ailto:mike.tutkow...@solidfire.com]
> > Sent: Thursday, February 07, 2013 9:29 AM
> > To: cloudstack-dev@incubator.apache.org
> > Cc: Edison Su
> > Subject: storage_refactor branch
> >
> > Hi Edison,
> >
> > I just wanted to confirm that I understo
: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Thursday, February 07, 2013 9:29 AM
> To: cloudstack-dev@incubator.apache.org
> Cc: Edison Su
> Subject: storage_refactor branch
>
> Hi Edison,
>
> I just wanted to confirm that I understood correctly tha
Hi Edison,
I just wanted to confirm that I understood correctly that the work being
done in the storage_refactor branch (to support storage plug-ins) is, in
fact, scheduled to be released with CloudStack 4.1.0.
As you know, I'm in the process of developing a plug-in for SolidFire. My
manag
29 matches
Mail list logo
