<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.lib.deltacloud.user">
    <title>gmane.comp.lib.deltacloud.user</title>
    <link>http://blog.gmane.org/gmane.comp.lib.deltacloud.user</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/19"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/18"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/17"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/16"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/15"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/14"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/13"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/12"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/11"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/10"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/9"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/8"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/7"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/6"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/5"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/4"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/3"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/2"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/1"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/19">
    <title>viewing the vm's console</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/19</link>
    <description>&lt;pre&gt;
Well at least in the portal i think it belongs. (vnc and/or spice for
RHEV for example). Suposse someone buys a vm with me:
They would very much like to be able to start/stop a vm, but also view
the console. What good would it do me to use the deltacloud portal, if i
also have to implement viewing the console in a different way?
Maybe i am understanding the project wrong?

Something like that would do it indeed, i guess.



&lt;/pre&gt;</description>
    <dc:creator>Sander Hoentjen</dc:creator>
    <dc:date>2009-12-03T07:16:08</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/18">
    <title>viewing the vm's console</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/18</link>
    <description>&lt;pre&gt;Hi Sander,

I would imagine it would be up to the provider to allow that,
deltacloud is a layer on top of the providers. And the console isnt
really part of a cloud api I think (And may be wrong :))

At RimuHosting we provide the console over ssh (as I suspect some
others do), I don't know how we would expose that over an API.

Unless it was just setting the password/public key for the
console-over-ssh, and getting ssh host/user connection details, Which
actually might work ok.

-ivan, http://rimuhosting.com

On Thu, Dec 3, 2009 at 12:29 AM, Sander Hoentjen &amp;lt;sander at hoentjen.eu&amp;gt; wrote:

&lt;/pre&gt;</description>
    <dc:creator>Ivan Meredith</dc:creator>
    <dc:date>2009-12-02T21:22:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/17">
    <title>viewing the vm's console</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/17</link>
    <description>&lt;pre&gt;Hi,

Deltacloud looks like a very interesting project. I have one question
though: Will deltacloud support the viewing of the vm's console? I
understand this will be difficult to implement, since different
hypervisors use a different protocol, but still i would be important to
have this ability.

Sander


&lt;/pre&gt;</description>
    <dc:creator>Sander Hoentjen</dc:creator>
    <dc:date>2009-12-02T11:29:46</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/16">
    <title>Libvirt deltacloud driver - does it makes sense?</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/16</link>
    <description>&lt;pre&gt;Hello,

Are there any plans to implement a libvirt driver for deltacloud? Idea
is to make it possible to do something like that:
1. Prepare a VM image templates to be run on fedora under KVM.
2. Create, start, stop, delete the virtual machines from the template
with deltacloud API.

Also, are there any plans for deltacloud builds to be available via
fedora repositories?

Thank you,
Roman

&lt;/pre&gt;</description>
    <dc:creator>Roman</dc:creator>
    <dc:date>2009-12-02T11:03:22</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/15">
    <title>Provider URL Error: Assistance required</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/15</link>
    <description>&lt;pre&gt;Michael, sorry for the lack response on that last one.  Frankly, I had
not been able to think of any other ideas without getting more
information.  None of us that have it set up have seen this particular
problem.  That said, now that you reminded me, I talked to one of the
other developers, and we are going to add some more useful debugging
information around those areas where the portal tries to connect to a
provider (mock or otherwise).  We'll try to get that in this week, and
I'll shoot you an email once it is commited (or you can just watch
deltacloud-devel for the patch/commit).

I did think of one other thing, just to make sure - you do have both
portal and framework/api running at the same time, correct?

-j

On Tue, Oct 20, 2009 at 4:19 PM, Michael Brown &amp;lt;mbrown1413 at gmail.com&amp;gt; wrote:



&lt;/pre&gt;</description>
    <dc:creator>Jason Guiditta</dc:creator>
    <dc:date>2009-10-20T22:07:36</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/14">
    <title>Provider URL Error: Assistance required</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/14</link>
    <description>&lt;pre&gt;Is there any more information I should include in order to make the problem
more clear?  Is there anything else you want for me to try?  I want to get
DeltaCloud up and running soon, but I can't figure this out.

Thanks,
   --Michael Brown

On Tue, Oct 13, 2009 at 11:00 AM, Michael Brown &amp;lt;mbrown1413 at gmail.com&amp;gt;wrote:

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://fedorahosted.org/pipermail/deltacloud-users/attachments/20091020/15f99a9e/attachment.html 

&lt;/pre&gt;</description>
    <dc:creator>Michael Brown</dc:creator>
    <dc:date>2009-10-20T20:19:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/13">
    <title>Provider URL Error: Assistance required</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/13</link>
    <description>&lt;pre&gt;I've tried both http://localhost:3000 and http://localhost:3000/api
Here is log from the portal after trying the latter:

provider url"]}, &amp;lt; at &amp;gt;base=#&amp;lt;Provider id: nil, name: "NEXT Services",
cloud_type: "Mock", url: "http://localhost:3000/api", lock_version: 0,
created_at: nil,updated_at: nil&amp;gt;&amp;gt;
task_target_type IS NULL)
task_target_type IS NULL)
task_target_type IS NULL)
task_target_type IS NULL)
task_target_type IS NULL)
task_target_type IS NULL)
task_target_type IS NULL)
task_target_type IS NULL)
task_target_type IS NULL)


[POST]
"url"=&amp;gt;"http://localhost:3000/api", "cloud_type"=&amp;gt;"Mock"}}
("providers"."name" = E'NEXT Services') LIMIT 1
http://127.0.0.1/provider/new]

Thanks for your help so far.  I'm excited about getting this working.h
    --Michael Brown

On Tue, Oct 6, 2009 at 3:09 PM, Jason Guiditta &amp;lt;jason.guiditta at gmail.com&amp;gt;wrote:

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://fedorahosted.org/pipermail/deltacloud-users/attachments/20091013/4cb4c1bc/attachment.html 

&lt;/pre&gt;</description>
    <dc:creator>Michael Brown</dc:creator>
    <dc:date>2009-10-13T15:00:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/12">
    <title>Provider URL Error: Assistance required</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/12</link>
    <description>&lt;pre&gt;Ok, I see two things here, responses inline

On Tue, Oct 6, 2009 at 12:00 PM, Michael Brown &amp;lt;mbrown1413 at gmail.com&amp;gt; wrote:
The above is an error because you need to input the same url you went
to in your browser.  Namely 'http://localhost:3000/api' rather than
'http://localhost:3000' as shown in the error above.  Now, if you
filled out the form with the url including '/api' and it is still
showing the error w/o it, that would be another issue, since it would
then not be receiving the same thing you submitted (which would
obviously be very weird).  I just verified on my own installation that
submitting the wrong url, then correcting it open the subsequent
attempt does post and create successfully as well.

This is just be _checking_ if the provider exists.  I see the same
thing in my log after creating a new provider.


&lt;/pre&gt;</description>
    <dc:creator>Jason Guiditta</dc:creator>
    <dc:date>2009-10-06T19:09:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/11">
    <title>Provider URL Error: Assistance required</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/11</link>
    <description>&lt;pre&gt;1. I've tried running the portal on both port 80 and 3001.
2. I have the developer version.
3. I can browse directly to the framework at http://localhost:3000/api.  As
far as I can tell the mock driver is working fine.
4. Here is the log from the portal:
provider url"]}, &amp;lt; at &amp;gt;base=#&amp;lt;Provider id: nil, name: "NEXT Services",
cloud_type:
updated_at: nil&amp;gt;&amp;gt;


04:49:34) [POST]
"url"=&amp;gt;"http://localhost:3000", "cloud_type"=&amp;gt;"Mock"}}
("providers"."name" = E'NEXT Services') LIMIT 1
http://deltacloud.cnl.ncsu.edu/provider/new]

Provider exists?  That's odd, there isn't anything in the database:

I can't figure out how this would be a database validation error.  I know
the framework isn't actually receiving any calls though, because it doesn't
show anything in the log.

Thanks for the help,
    --Michael Brown

On Thu, Oct 1, 2009 at 4:01 PM, Jason Guiditta &amp;lt;jason.guiditta at gmail.com&amp;gt;wrote:

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://fedorahosted.org/pipermail/deltacloud-users/attachments/20091006/eea9f152/attachment.html 

&lt;/pre&gt;</description>
    <dc:creator>Michael Brown</dc:creator>
    <dc:date>2009-10-06T16:00:37</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/10">
    <title>Provider URL Error: Assistance required</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/10</link>
    <description>&lt;pre&gt;
I just tried this with -b set for both framework and portal w/o issue.
 Of the urls above that you tried, http://localhost:3000/api should
definitely work.  That is a database validation error you are seeing,
which seems odd.  Couple details:
1. You have framework running on port 3000, what about portal?
2. Did you install the developer version rather than rpm?  (looks like
that is the case)
3. Can you browse directly to http://localhost:3000/api?  If not, what
happens and what does the framework log look like?
4. Please provide more of the log from portal when you try to add a provider

&lt;/pre&gt;</description>
    <dc:creator>Jason Guiditta</dc:creator>
    <dc:date>2009-10-01T20:01:33</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/9">
    <title>Provider URL Error: Assistance required</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/9</link>
    <description>&lt;pre&gt;We're trying to install and run deltacloud, but ran into problems.  We have
the framework and the portal both running.  But when we went to the portal
url and tried to add a cloud provider there, it complained about the url:


Iptables and SELinux is disabled.  We've tried urls
http://localhost:3000/api, http://localhost:3000/, http://127.0.0.1:3000/api
, http://127.0.0.1:3000/

We're starting the framework using the mock driver as follows:


Thanks,
  Michael Brown
  --Next Services
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://fedorahosted.org/pipermail/deltacloud-users/attachments/20091001/b24cd66d/attachment.html 

&lt;/pre&gt;</description>
    <dc:creator>Michael Brown</dc:creator>
    <dc:date>2009-10-01T18:42:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/8">
    <title>Common API to access other cloud services/resources (e.g. Cloud DBs, Storage or Queues)</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/8</link>
    <description>&lt;pre&gt;Hi guys,

I have a very general question. How do you see the future of DeltaCloud in  
terms of accessing cloud resources such as Database system, etc?

It would be quite "interesting" to run a select-like statement on eg Amazon  
SimpleDB using your Delta's REST API. But it wouldn't be too efficient,  
would it?

Is DeltaCloud targeting only Cloud Management Tools (similar to eg  
enStratus) or is it also going in the direction of supporting  
the "independence" of applications running on the cloud.

thanks for sharing your thoughts,
Adam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://fedorahosted.org/pipermail/deltacloud-users/attachments/20090918/ef0c6153/attachment.html 

&lt;/pre&gt;</description>
    <dc:creator>Unknown</dc:creator>
    <dc:date>2009-09-18T13:54:22</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/7">
    <title>Does each Deltacloud framework instance could only have one driver?</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/7</link>
    <description>&lt;pre&gt;

Sorry.. I pushed them to the wrong repo. They are up there now.

&lt;/pre&gt;</description>
    <dc:creator>Bryan Kearney</dc:creator>
    <dc:date>2009-09-11T12:38:36</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/6">
    <title>Does each Deltacloud framework instance could only have one driver?</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/6</link>
    <description>&lt;pre&gt;Have these informations be put into docs repository? I have issue such
command:
git clone git://git.fedorahosted.org/git/deltacloud/docs.git/
But didn`t get this information from any file of docs directory.

&lt;/pre&gt;</description>
    <dc:creator>Yufang Zhang</dc:creator>
    <dc:date>2009-09-11T04:03:46</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/5">
    <title>Does each Deltacloud framework instance could only have one driver?</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/5</link>
    <description>&lt;pre&gt;This is what I have added to the docs section. Please let me know what
other questions you have. I am not 100% clear on the RHEV-M setup.

The RHEV-M driver needs to be installed on a Windows machine which has
the RHEV-M Powershell API installed and configured. Assuming the
directory structure above is followed, you should copy the file
deltacloud/deltacloud-driver-rhevm/config/rhevm_config.yaml.EXAMPLE to
be rhevm_config.yaml and edit the file woith the domain you are logging
into. The username and pasword is provided via the API.

The actual RHEVM instance you are connecting to is controlled by
the RHEVM.dll.config file which is referenced from the profile.ps1
file located in My Documents/WindowsPowershell directory.


&lt;/pre&gt;</description>
    <dc:creator>Bryan Kearney</dc:creator>
    <dc:date>2009-09-10T14:11:46</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/4">
    <title>Does each Deltacloud framework instance could only have one driver?</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/4</link>
    <description>&lt;pre&gt;I see Bryan responded on the RHEVM docs already, but the answer to your
other question is, for now, yes.  You do need to start multiple frameworks
to talk to multiple providers.  However this setup will be improved in the
near future.

-j

2009/9/9 Yufang Zhang &amp;lt;yufang_zhang5 at yahoo.com.cn&amp;gt;

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://fedorahosted.org/pipermail/deltacloud-users/attachments/20090910/174b2df4/attachment.html 

&lt;/pre&gt;</description>
    <dc:creator>Jason Guiditta</dc:creator>
    <dc:date>2009-09-10T14:02:25</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/3">
    <title>Does each Deltacloud framework instance could only have onedriver?</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/3</link>
    <description>&lt;pre&gt;Docs being lax are my fault. I will update them today and send out an 
email when complete.

&lt;/pre&gt;</description>
    <dc:creator>Bryan Kearney</dc:creator>
    <dc:date>2009-09-10T12:18:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/2">
    <title>Does each Deltacloud framework instance could only have one driver?</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/2</link>
    <description>&lt;pre&gt;Hi guys,

It is fantastic that this is maybe the first mail in the list:) I am a 
newbie of deltacloud. I have setup the framework of deltacloud on my 
fedora 11 host, with mock as its default driver. And also I installed 
portal of deltacloud through which I can manage instances and images.

But I`d like to konw if each Deltacloud framework instance could only 
have one driver(mock or rhev-m or ec2). In other words, if you want to 
work with multiple different clouds, is it compulsory that you have to 
start multiple framework instances, each of which has its own default 
driver(and the only driver)?

BTW,could anybody give some information on how to get work with RHEV-M 
driver? It seems that neither of the READMEs of framework or portal has 
covered this.

Thank you in advance.

--Yuzhang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://fedorahosted.org/pipermail/deltacloud-users/attachments/20090910/ca24ce54/attachment.html 

&lt;/pre&gt;</description>
    <dc:creator>Yufang Zhang</dc:creator>
    <dc:date>2009-09-10T00:51:31</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/1">
    <title>Does each Deltacloud framework instance could only have one driver?</title>
    <link>http://permalink.gmane.org/gmane.comp.lib.deltacloud.user/1</link>
    <description>&lt;pre&gt;Hi guys,

It is fantastic that this is maybe the first mail in the list:) I am a newbie of deltacloud. I have setup the framework of deltacloud on my fedora 11 host, with mock as its default driver. And also I installed portal  of deltacloud through which I can manage instances and images.

But I`d like to konw if  each Deltacloud framework instance could only have one driver(mock or rhev-m or ec2). In other words, if you want to work with multiple different clouds, is it compulsory that you have to start multiple  framework instances, each of which has its own default driver(and the only driver)?

BTW,could anybody give some information on how to get work with RHEV-M driver? It seems that neither of the READMEs of framework or portal has covered this.

Thank you in advance.

--Yuzhang
 


      ___________________________________________________________ 
  ????????????????? 
http://card.mail.cn.yahoo.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://fedorahosted.org/pipermail/deltacloud-users/attachments/20090909/fd13bf44/attachment.html 

&lt;/pre&gt;</description>
    <dc:creator>Yufang Zhang</dc:creator>
    <dc:date>2009-09-09T16:30:41</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.lib.deltacloud.user">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.lib.deltacloud.user</link>
  </textinput>
</rdf:RDF>

