Hey All.
One of the things which I would like to add in is the ability to pass ing forward DNS details and let deltacloud take care of setting it up against one of the public IPs when it knows it. I am not really sure if this is a deltacloud thing - unfortunately it looks like EC2 doesn't provide something like this for you (it has elastic IPs, but that is kind of different), but rackspace does. There are things like ez-ipupdate utilities that you can use to hook in to a wide variety of public dyn DNS things, and of course private servers.
Is this something of interest or appropriate to deltacloud? it is certainly relevant to a lot of what some of us need to do, would be nice to have it abstracted into some part of the drivers.
Unfortunately, not much we can do about reverse DNS as it is up to who owns the IPs, so with Amazon, I believe the term is "SOL", but at least with forward resolution, that is something (no good for the spammer though!).
Thoughts? If people are interested, I might nock something up to see how it might work.
On Thu, Oct 15, 2009 at 7:38 AM, Michael Neale michael.neale@gmail.com wrote:
Hey All.
One of the things which I would like to add in is the ability to pass ing forward DNS details and let deltacloud take care of setting it up against one of the public IPs when it knows it. I am not really sure if this is a deltacloud thing - unfortunately it looks like EC2 doesn't provide something like this for you (it has elastic IPs, but that is kind of different), but rackspace does. There are things like ez-ipupdate utilities that you can use to hook in to a wide variety of public dyn DNS things, and of course private servers.
Is this something of interest or appropriate to deltacloud? it is certainly relevant to a lot of what some of us need to do, would be nice to have it abstracted into some part of the drivers.
Unfortunately, not much we can do about reverse DNS as it is up to who owns the IPs, so with Amazon, I believe the term is "SOL", but at least with forward resolution, that is something (no good for the spammer though!).
Thoughts? If people are interested, I might nock something up to see how it might work.
-- Michael D Neale home: www.michaelneale.net blog: michaelneale.blogspot.com _______________________________________________ deltacloud-devel mailing list deltacloud-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/deltacloud-devel
Michael, sorry for the delayed response. I am not sure exactly what you have in mind here, but I talked to Hugh, and he said 'we want something similar to EC2 security groups' and that any dns goodness woudl be great to have. If you wanted to nock something up,as you mentioned, it would be greatly appreciated, and probably easier to give feedback on (being something more concrete).
Hi Jason.
Yes amazon have a few things like that, including elastic IPs etc..
But what I was more interested in was from the application deployment perspective, no so much infrastructure: ie I would like to deploy apps but also setup the preferred names/dns entries for them in a simplified way. So if I have a domain setup:
myco.com - then via deltacloud I can create an instance and bind it to whizzbang.myco.com etc... should a suitable DNS service be available. Amazon I think returns names already, Rackspace does public IPs etc.. (this is all about the public address part of deltacloud).
To be honest I am not entirely sure what form this would take, its more a "desire" from a users point of view !
This would have to be an addition to the drivers, such that you could request a binding to a name be made (which may be ignored). However, I am not sure if enough cloud providers have the facilities to do this to make it worthwhile putting in the driver part of deltacloud (otherwise it could have separate drivers for the various ways people manage DNS).
Or perhaps deltacloud is not the place for this, and its really something to be built on the top/side?
On Sat, Oct 24, 2009 at 8:04 AM, Jason Guiditta jason.guiditta@gmail.com wrote:
On Thu, Oct 15, 2009 at 7:38 AM, Michael Neale michael.neale@gmail.com wrote:
Hey All.
One of the things which I would like to add in is the ability to pass ing forward DNS details and let deltacloud take care of setting it up against one of the public IPs when it knows it. I am not really sure if this is a deltacloud thing - unfortunately it looks like EC2 doesn't provide something like this for you (it has elastic IPs, but that is kind of different), but rackspace does. There are things like ez-ipupdate utilities that you can use to hook in to a wide variety of public dyn DNS things, and of course private servers.
Is this something of interest or appropriate to deltacloud? it is certainly relevant to a lot of what some of us need to do, would be nice to have it abstracted into some part of the drivers.
Unfortunately, not much we can do about reverse DNS as it is up to who owns the IPs, so with Amazon, I believe the term is "SOL", but at least with forward resolution, that is something (no good for the spammer though!).
Thoughts? If people are interested, I might nock something up to see how it might work.
-- Michael D Neale home: www.michaelneale.net blog: michaelneale.blogspot.com _______________________________________________ deltacloud-devel mailing list deltacloud-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/deltacloud-devel
Michael, sorry for the delayed response. I am not sure exactly what you have in mind here, but I talked to Hugh, and he said 'we want something similar to EC2 security groups' and that any dns goodness woudl be great to have. If you wanted to nock something up,as you mentioned, it would be greatly appreciated, and probably easier to give feedback on (being something more concrete).
--
-j
We have our own dns api at RimuHosting, and use FQDN's for instance names, so I could already set up DNS automatically if I wanted to. However we would obviously need to be authoritative for the domain names to make any difference. Due the the large variety of DNS providers among our customers, I'm not sure how this would work. (Although a decent amount of people use our service, that might only be 20%, although I'm not sure)
I think that as a user of the Delta Cloud api, I can make my own calls to setup DNS if I so wish. I know its not a generic way, however individual users are more likely to have there DNS with one provider (possibly), and therefore are not in need of a generic solution.
-Ivan
2009/10/26 Michael Neale michael.neale@gmail.com
Hi Jason.
Yes amazon have a few things like that, including elastic IPs etc..
But what I was more interested in was from the application deployment perspective, no so much infrastructure: ie I would like to deploy apps but also setup the preferred names/dns entries for them in a simplified way. So if I have a domain setup:
myco.com - then via deltacloud I can create an instance and bind it to whizzbang.myco.com etc... should a suitable DNS service be available. Amazon I think returns names already, Rackspace does public IPs etc.. (this is all about the public address part of deltacloud).
To be honest I am not entirely sure what form this would take, its more a "desire" from a users point of view !
This would have to be an addition to the drivers, such that you could request a binding to a name be made (which may be ignored). However, I am not sure if enough cloud providers have the facilities to do this to make it worthwhile putting in the driver part of deltacloud (otherwise it could have separate drivers for the various ways people manage DNS).
Or perhaps deltacloud is not the place for this, and its really something to be built on the top/side?
On Sat, Oct 24, 2009 at 8:04 AM, Jason Guiditta jason.guiditta@gmail.com wrote:
On Thu, Oct 15, 2009 at 7:38 AM, Michael Neale michael.neale@gmail.com
wrote:
Hey All.
One of the things which I would like to add in is the ability to pass ing forward DNS details and let deltacloud take care of setting it up against one of the public IPs when it knows it. I am not really sure if this is a deltacloud thing - unfortunately it looks like EC2 doesn't provide something like this for you (it has elastic IPs, but that is kind of different), but rackspace does. There are things like ez-ipupdate utilities that you can use to hook in to a wide variety of public dyn DNS things, and of course private servers.
Is this something of interest or appropriate to deltacloud? it is certainly relevant to a lot of what some of us need to do, would be nice to have it abstracted into some part of the drivers.
Unfortunately, not much we can do about reverse DNS as it is up to who owns the IPs, so with Amazon, I believe the term is "SOL", but at least with forward resolution, that is something (no good for the spammer though!).
Thoughts? If people are interested, I might nock something up to see how it might work.
-- Michael D Neale home: www.michaelneale.net blog: michaelneale.blogspot.com _______________________________________________ deltacloud-devel mailing list deltacloud-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/deltacloud-devel
Michael, sorry for the delayed response. I am not sure exactly what you have in mind here, but I talked to Hugh, and he said 'we want something similar to EC2 security groups' and that any dns goodness woudl be great to have. If you wanted to nock something up,as you mentioned, it would be greatly appreciated, and probably easier to give feedback on (being something more concrete).
--
-j
-- Michael D Neale home: www.michaelneale.net blog: michaelneale.blogspot.com _______________________________________________ deltacloud-devel mailing list deltacloud-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/deltacloud-devel
On Mon, Oct 26, 2009 at 07:11:51PM +1300, Ivan Meredith wrote:
We have our own dns api at RimuHosting, and use FQDN's for instance names, so I could already set up DNS automatically if I wanted to. However we would obviously need to be authoritative for the domain names to make any difference. Due the the large variety of DNS providers among our customers, I'm not sure how this would work. (Although a decent amount of people use our service, that might only be 20%, although I'm not sure)
I think that as a user of the Delta Cloud api, I can make my own calls to setup DNS if I so wish. I know its not a generic way, however individual users are more likely to have there DNS with one provider (possibly), and therefore are not in need of a generic solution.
-Ivan
Hmm OK. Perhaps it's still something we would eventually want to add to the portal though?
In any case, we *do* need to start thinking about what shape the network management API is going to take...
--Hugh
2009/10/26 Michael Neale michael.neale@gmail.com
Hi Jason.
Yes amazon have a few things like that, including elastic IPs etc..
But what I was more interested in was from the application deployment perspective, no so much infrastructure: ie I would like to deploy apps but also setup the preferred names/dns entries for them in a simplified way. So if I have a domain setup:
myco.com - then via deltacloud I can create an instance and bind it to whizzbang.myco.com etc... should a suitable DNS service be available. Amazon I think returns names already, Rackspace does public IPs etc.. (this is all about the public address part of deltacloud).
To be honest I am not entirely sure what form this would take, its more a "desire" from a users point of view !
This would have to be an addition to the drivers, such that you could request a binding to a name be made (which may be ignored). However, I am not sure if enough cloud providers have the facilities to do this to make it worthwhile putting in the driver part of deltacloud (otherwise it could have separate drivers for the various ways people manage DNS).
Or perhaps deltacloud is not the place for this, and its really something to be built on the top/side?
On Sat, Oct 24, 2009 at 8:04 AM, Jason Guiditta jason.guiditta@gmail.com wrote:
On Thu, Oct 15, 2009 at 7:38 AM, Michael Neale michael.neale@gmail.com
wrote:
Hey All.
One of the things which I would like to add in is the ability to pass ing forward DNS details and let deltacloud take care of setting it up against one of the public IPs when it knows it. I am not really sure if this is a deltacloud thing - unfortunately it looks like EC2 doesn't provide something like this for you (it has elastic IPs, but that is kind of different), but rackspace does. There are things like ez-ipupdate utilities that you can use to hook in to a wide variety of public dyn DNS things, and of course private servers.
Is this something of interest or appropriate to deltacloud? it is certainly relevant to a lot of what some of us need to do, would be nice to have it abstracted into some part of the drivers.
Unfortunately, not much we can do about reverse DNS as it is up to who owns the IPs, so with Amazon, I believe the term is "SOL", but at least with forward resolution, that is something (no good for the spammer though!).
Thoughts? If people are interested, I might nock something up to see how it might work.
-- Michael D Neale home: www.michaelneale.net blog: michaelneale.blogspot.com _______________________________________________ deltacloud-devel mailing list deltacloud-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/deltacloud-devel
Michael, sorry for the delayed response. I am not sure exactly what you have in mind here, but I talked to Hugh, and he said 'we want something similar to EC2 security groups' and that any dns goodness woudl be great to have. If you wanted to nock something up,as you mentioned, it would be greatly appreciated, and probably easier to give feedback on (being something more concrete).
--
-j
-- Michael D Neale home: www.michaelneale.net blog: michaelneale.blogspot.com _______________________________________________ deltacloud-devel mailing list deltacloud-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/deltacloud-devel
deltacloud-devel mailing list deltacloud-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/deltacloud-devel
Hmm OK. Perhaps it's still something we would eventually want to add to the portal though?
Perhaps - at least the configuration side of it to help people set it up but it really be nice to have name binding in a concise deltacloud level api, that is my dream anyway ;)
In any case, we *do* need to start thinking about what shape the network management API is going to take...
--Hugh
My initial thoughts (plus having only cursorily scanned this thread) is that...
DNS is external to "the cloud" and applied to it from some other location.
IP management is internal to "the cloud".
A value-add such as dyndns.org interaction could be useful, I reckon.
Or some standardized POST-back when IPs change, or somesuch, maybe. But then we're getting into the whole waters of callback notifications over HTTP, and the state related to such, plus the facilities to provide such behavior.
How does Rackspace's IP-management compare to EC2's or Rimu's?
Let's analyse what's possible given existing providers, then see what the feature-set really is, to start with.
-Bob
On Oct 28, 2009, at 6:32 PM, Michael Neale wrote:
Hmm OK. Perhaps it's still something we would eventually want to add to the portal though?
Perhaps - at least the configuration side of it to help people set it up but it really be nice to have name binding in a concise deltacloud level api, that is my dream anyway ;)
In any case, we *do* need to start thinking about what shape the network management API is going to take...
--Hugh
deltacloud-devel mailing list deltacloud-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/deltacloud-devel
We basically have a primary IP, and then 0-N secondary IPs. (Usually in the same /24).
Sometimes we will do private IPs for customers on dedicated servers.. but this is just on an ad-hoc basis, and not really supported.
We assign IPs automatically, the user doesn't get a choice (spammers would love the choice).
Nothing the lie amazon elastic IP stuff. But that might come in the future.
-Ivan http://rimuhosting.com
2009/10/29 Bob McWhirter bmcwhirt@redhat.com
My initial thoughts (plus having only cursorily scanned this thread) is that...
DNS is external to "the cloud" and applied to it from some other location.
IP management is internal to "the cloud".
A value-add such as dyndns.org interaction could be useful, I reckon.
Or some standardized POST-back when IPs change, or somesuch, maybe. But then we're getting into the whole waters of callback notifications over HTTP, and the state related to such, plus the facilities to provide such behavior.
How does Rackspace's IP-management compare to EC2's or Rimu's?
Let's analyse what's possible given existing providers, then see what the feature-set really is, to start with.
-BobOn Oct 28, 2009, at 6:32 PM, Michael Neale wrote:
Hmm OK. Perhaps it's still something we would eventually want to add to the portal though?
Perhaps - at least the configuration side of it to help people set it up but it really be nice to have name binding in a concise deltacloud level api, that is my dream anyway ;)
In any case, we *do* need to start thinking about what shape the network management API is going to take...
--Hugh
deltacloud-devel mailing list deltacloud-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/deltacloud-devel
deltacloud-devel mailing list deltacloud-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/deltacloud-devel
Apparently EC2 doesn't have anything like it. Rackspace have something - but I am not sure if this can be tied down per driver, but is a separate thing to the cloud providers....
On further reflection, what I really mean (as in *like*) is Subdomains: http://en.wikipedia.org/wiki/Subdomain
So lets say bob owns humbucker.com - so in a reasonable cloud setup, that would be setup "out of band". What would be nice would be that we can do a create_instance, and then bind that to:
dimarzio1.humbucker.com etc... and have it create the entry (probably on the DNS server that the cloud controls, maybe).
Thoughts? Anyone who knows about this stuff care to comment?
On Thu, Oct 29, 2009 at 12:56 PM, Bob McWhirter bmcwhirt@redhat.com wrote:
My initial thoughts (plus having only cursorily scanned this thread) is that...
DNS is external to "the cloud" and applied to it from some other location.
IP management is internal to "the cloud".
A value-add such as dyndns.org interaction could be useful, I reckon.
Or some standardized POST-back when IPs change, or somesuch, maybe. But then we're getting into the whole waters of callback notifications over HTTP, and the state related to such, plus the facilities to provide such behavior.
How does Rackspace's IP-management compare to EC2's or Rimu's?
Let's analyse what's possible given existing providers, then see what the feature-set really is, to start with.
-Bob
On Oct 28, 2009, at 6:32 PM, Michael Neale wrote:
Hmm OK. Perhaps it's still something we would eventually want to add to the portal though?
Perhaps - at least the configuration side of it to help people set it up but it really be nice to have name binding in a concise deltacloud level api, that is my dream anyway ;)
In any case, we *do* need to start thinking about what shape the network management API is going to take...
--Hugh
deltacloud-devel mailing list deltacloud-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/deltacloud-devel
deltacloud-devel@lists.fedorahosted.org
-
Bob McWhirter -
Hugh O. Brock -
Ivan Meredith -
jason.guiditta -
Michael Neale