[openstack-dev] DNS and Designate mid-cycle meet-up - August in Austin

2015-07-20 Thread Joe Mcbride
Hello,
The Designate team will hold it's mid-cycle meet-up in August, details below.
 - Dates: August 17 to 20, 2015
 - Location: Austin TX
 - Registration/agenda: 
http://www.eventbrite.co.uk/e/openstack-designate-2015-summer-mid-cycle-meetup-tickets-17833181526
 - Remote attendees are welcome and will be accommodated via Google Hangout.

Learn more about Designate:
 - Docs: http://docs.openstack.org/developer/designate/getting-started.html
 - Wiki: https://wiki.openstack.org/wiki/Designate
 - IRC: #openstack-dns (everyday) and Wednesday @17:00UTC on 
#openstack-meeting-alt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Neutron] - Joining the team - interested in a Debian Developer and experienced Python and Network programmer?

2015-04-13 Thread Joe Mcbride
My apologies to the list. This was not intended to be broadcast.



From: Joe Mcbride
Sent: Monday, April 13, 2015 12:42 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron] - Joining the team - interested in a 
Debian Developer and experienced Python and Network programmer?

Hi Matt,
Our team at Rackspace is looking to add a developer, focused on building out 
and deploying Designate (DNSaaS for Openstack). When we go live, we expect to 
have the largest public deployment, so scaling and migration challenges will be 
particularly interesting technical problems to solve.

Best of luck on getting into the Neutron fun.

__
Joe McBride
Rackspace Cloud DNS
I’m hiring a software developer 
https://gist.github.com/joeracker/d49030cef6001a8f94d0



From: Matt Grant m...@mattgrant.net.nz
Sent: Thursday, April 9, 2015 2:13 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Neutron] - Joining the team - interested in a Debian 
Developer and experienced Python and Network programmer?

Hi!

I am just wondering what the story is about joining the neutron team.
Could you tell me if you are looking for new contributors?

Previously I have programmed OSPFv2 in Zebra/Quagga, and worked as a
router developer for Allied Telesyn.  I also have extensive Python
programming experience, having worked on the DNS Management System.

I have been experimenting with IPv6 since 2008 on my own home network,
and I am currently installing a Juno Openstack cluster to learn ho
things tick.

Have you guys ever figured out how to do a hybrid L3 North/South Neutron
router that propagates tenant routes and networks into OSPF/BGP via a
routing daemon, and uses floating MAC addresses/costed flow rules via
OVS to fail over to a hot standby router? There are practical use cases
for such a thing in smaller deployments.

I have a single stand alone example working by turning off
neutron-l3-agent network name space support, and importing the connected
interface and static routes into Bird and Birdv6. The AMPQ connection
back to the neutron-server is via the upstream interface and is secured
via transport mode IPSEC (just easier than bothering with https/SSL).
Bird looks easier to run from neutron as they are single process than a
multi process Quagga implementation.  Incidentally, I am running this in
an LXC container.

Could some one please point me in the right direction.  I would love to
be in Vancouver :-)

Best Regards,

--
Matt Grant,  Debian and Linux Systems Administration and Consulting
Mobile: 021 0267 0578
Email: m...@mattgrant.net.nz


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Neutron] - Joining the team - interested in a Debian Developer and experienced Python and Network programmer?

2015-04-13 Thread Joe Mcbride
Hi Matt,
Our team at Rackspace is looking to add a developer, focused on building out 
and deploying Designate (DNSaaS for Openstack). When we go live, we expect to 
have the largest public deployment, so scaling and migration challenges will be 
particularly interesting technical problems to solve.

Best of luck on getting into the Neutron fun.

__
Joe McBride
Rackspace Cloud DNS
I’m hiring a software developer 
https://gist.github.com/joeracker/d49030cef6001a8f94d0



From: Matt Grant m...@mattgrant.net.nz
Sent: Thursday, April 9, 2015 2:13 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Neutron] - Joining the team - interested in a Debian 
Developer and experienced Python and Network programmer?

Hi!

I am just wondering what the story is about joining the neutron team.
Could you tell me if you are looking for new contributors?

Previously I have programmed OSPFv2 in Zebra/Quagga, and worked as a
router developer for Allied Telesyn.  I also have extensive Python
programming experience, having worked on the DNS Management System.

I have been experimenting with IPv6 since 2008 on my own home network,
and I am currently installing a Juno Openstack cluster to learn ho
things tick.

Have you guys ever figured out how to do a hybrid L3 North/South Neutron
router that propagates tenant routes and networks into OSPF/BGP via a
routing daemon, and uses floating MAC addresses/costed flow rules via
OVS to fail over to a hot standby router? There are practical use cases
for such a thing in smaller deployments.

I have a single stand alone example working by turning off
neutron-l3-agent network name space support, and importing the connected
interface and static routes into Bird and Birdv6. The AMPQ connection
back to the neutron-server is via the upstream interface and is secured
via transport mode IPSEC (just easier than bothering with https/SSL).
Bird looks easier to run from neutron as they are single process than a
multi process Quagga implementation.  Incidentally, I am running this in
an LXC container.

Could some one please point me in the right direction.  I would love to
be in Vancouver :-)

Best Regards,

--
Matt Grant,  Debian and Linux Systems Administration and Consulting
Mobile: 021 0267 0578
Email: m...@mattgrant.net.nz


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] OpenStack Designate DNSaaS

2014-06-18 Thread Joe Mcbride
Brad,
It seems to me you have a classic migration problem on your hands.
Assuming your ideal end state is to completely migrate to Designate and
minimize customizations (which is definitely preferable for the long
term), your strategy is the real challenge.

One approach is to deploy Designate and put all new domains and or tenants
there.  Over time, migrate domains and tenants over. Your consumers will
naturally want the new benefits and hopefully facilitate the changes.

Another is to have an old fashioned ³cut over². There is considerable risk
which can be mitigated by if your domains don¹t change often and your
consumer base is aligned.

Alternatively, you can run both in parallel and sink between them at the
database layer until you can ultimately switch users over.  This approach
is only recommended if you have to support an older API on the previous
system. You can also synchronize to the same set of name servers if you
can not change them. The problem with this approach is you will write a
lot of throw-a-way code.

SOME QUESTIONS:
- Is there an API available to your current system for your consumers? If
no, that greatly simplifies things.
- Can you easily change your name servers with your registrars?
- Why bother keeping the old system around?


On 6/17/14, 4:38 PM, Hayes, Graham graham.ha...@hp.com wrote:

Unfortunately #1 is not a real option - designate needs the storage layer
to operate.

I would guess #2 or #3 would be the more feasible options.

Graham


MIDGLEY, BRAD bm9...@att.com wrote:



PK,

I¹d agree with pursuing #1 or with a simple reference implementation like
minidns if ripping it out is disruptive.

Brad

_
From: ESWARAN, PK
Sent: Tuesday, June 17, 2014 1:26 PM
To: openstack-dev@lists.openstack.org; Graham Hayes
(graham.ha...@hp.com); Kiall Mac Innes (ki...@hp.com)
Cc: PACHECO, RODOLFO J; JALLI, RANDEEP; O'CONNELL, MATT; MICHALEK, KEN;
MIDGLEY, BRAD; BISHOP, JAMES; 'raymond.h...@accenture.com'
(raymond.h...@accenture.com); BOEHMER, JEFF; SCOLLARD, JAMES; SHANGHAVI,
PRAFUL B
Subject: OpenStack Designate DNSaaS


Dear OpenStack Dev Team:
I exchanged a few thoughts on Designate DNSaaS with Graham Hayes
of HP and he advised me to send this out to a larger DEV audience. Your
feedback will help the Designte DNSaaS project and also the ATT Cloud
group.

ATT Cloud group is investigating ³Designate DNSaaS² and we would like to
indulge in this emerging technology. We could embrace and also
participate into this new OpenStack technology. I am also copying a few
of the ATT team members.

In ATT in the near term, we would like to use Designate DNSaaS as a
frontend while retaining the current ATT backend DNS infrastructure in
place. The main issue in this is the role of ³Designate Database² as
MASTER database of record for all Designate DNS provisioning. This
Designate role is useful when there is a deployment of new DNS system and
auth servers. But Š.

In ATT, we already have a ³DNS bind provisioner and a database of
record² that keeps our DNS authoritative servers updated. Having a dual
DNS Master Databases of record will be a synchronizing nightmare and it
will be a difficult, time consuming process to reposition our existing
BIND auth servers DIRECTLY under Designate.

Please also note that the exisitng ATT ³DNS bind provisioner and
a database of record² handles multiple services and multiple customers
within each service while validating the rightful ownership prior to any
DNS manipulations.

In the near term we would like to engage in a LESS-THAN-fork-lift
effort so that we can enjoy the major functions of ³Designate API²,
³Designate Central² and ³Designate Sink².

So the question is what are our alternatives without a fork-lift
effort?

Knowing that the Designate storage layer is pluggable, I was
looking at the following possibilities and your feedback could help us.
Thank you in advance.


  1.  Disable the storage layer entirely while keeping it for minimal
essential Designate functions.
  2.  Writing a storage plugin to our existing DB may be one
consideration, but this would require a fork-lift effort since the
current system supports multiple services and customers. This would take
a longer timeframe than what we want to ensure that things are OK.
  3.  Writing a storage-plugin-backend to a system-process that in turn
will manage our existing DB, seems to be a good possibility but this is
not yet clear.
  4.  ?? Possibly other with your feedback. Thanks.


P.K. Eswaran
ATT Information Technology Operations
Middletown, NJ
Room C1-2B06
pk.eswa...@att.commailto:pk.eswa...@att.com
pe3...@att.commailto:pe3...@att.com
(732) 420-2175




___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list

Re: [openstack-dev] OpenStack Designate DNSaaS

2014-06-18 Thread Joe Mcbride

On 6/18/14, 12:51 PM, O'CONNELL, MATT mo1...@att.com wrote:

I think the thinking was the ATT DNS backend was more desirable
(hardened, load balanced, global, configurable,
non-prototype, 30 second updates), so the idea was to go around the
Designate DNS function and
call the ATT DNS API and use the Designate for customer and other non DNS
function points. I think that is the plan for CORA.

I definitely agree that is a plausible approach and Designate should be
able to accommodate customers with a running set of authoritative name
servers (assuming supported makes/versions of name servers) as you
describe.

OP’s challenge is greater than keeping their current backend, they have a
database of record” to manage.
 In ATT, we already have a ³DNS bind provisioner and a database of
 record² that keeps our DNS authoritative servers updated.


My feeling is that eliminating that database would be a better long term
solution as it minimizes upgrade complexity.

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [designate] FW: The Decline and Fall of Bind 10

2014-05-14 Thread Joe Mcbride


On 5/14/14, 1:33 PM, Mike Sisk mike.s...@rackspace.com wrote:

https://ripe68.ripe.net/presentations/208-The_Decline_and_Fall_of_BIND_10.
pdf


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [designate] meeting in room 203 for more design work

2014-05-14 Thread Joe Mcbride
Sorry, I misspelled ³designate² (again) last time I sent this.

On 5/14/14, 4:21 PM, Joe Mcbride jmcbr...@rackspace.com wrote:

Hello all,
If you are still at the conference today (May 14), we invite you to join
us in room 203 at the Openstack conference.

We will be working through the following:
https://etherpad.openstack.org/p/juno-design-summit-designate-session-3


Cheers,
joe



___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [desigante] meeting in room 203 for more design work

2014-05-14 Thread Joe Mcbride
Hello all,
If you are still at the conference today (May 14), we invite you to join
us in room 203 at the Openstack conference.

We will be working through the following:
https://etherpad.openstack.org/p/juno-design-summit-designate-session-3


Cheers,
joe


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [designate] Windows problem with install workshop VM

2014-05-12 Thread Joe Mcbride
The following command created a virtual box compatible files:
tar xopft designate-workshop_virtualbox.box

I was then able to import the box.ovf file and run it in VirtualBox
('vagrant/vagrant' for user/pass).  Can someone with access to a windows
machine give it a run? We can consider this for those running windows.


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Neutron][Nova][Designate][L3][IPv6] Discussion about Cross-Project Integration of DNS at Summit

2014-05-12 Thread Joe Mcbride
Hi all,
Members of the Designate project are in room 203 at the Neutron pod. Look
forward to meeting you all.

On 5/9/14, 9:17 AM, Hayes, Graham graham.ha...@hp.com wrote:

Hi,

It looks like us 'none ATC' folk will have access to the project pods -
so should we nail down a time on Monday?

It looks like the 16:30 onwards is the most popular choice - will we say
16:30 on Monday in the Neutron pod?

Thanks,

Graham

On Tue, 2014-05-06 at 17:45 +, Veiga, Anthony wrote:
Hi,

The only issue I would see with the pod is that not all of us are ATCs,
so we may or may not have access to that area (I am open to correction on
that point - in fact I hope someone does ;) )


I¹ll second this.  I have an interest in attending and assisting here,
but I don¹t have ATC status yet (though I¹m an active contributor
technically, just not via code.)




I could see it fitting in with our design session, but maybe if we meet
on the Monday to do some initial hashing out as well, I think that would
be good.

I am around for the morning, and later on in the afternoon on Monday, if
that suits.

Graham

On Tue, 2014-05-06 at 11:21 -0600, Carl Baldwin wrote:


I have just updated my etherpad [1] with some proposed times.  Not
knowing much about the venue, I could only propose the pod area as a
the location.

I also updated the designate session etherpad [2] per your suggestion.
 If there is time during the Designate sessions to include this in the
discussion then that may work out well.

Thanks,
Carl

[1] https://etherpad.openstack.org/p/juno-dns-neutron-nova-designate
[2] https://etherpad.openstack.org/p/DesignateAtlantaDesignSession

On Tue, May 6, 2014 at 8:58 AM, Joe Mcbride
jmcbr...@rackspace.commailto:jmcbr...@rackspace.com wrote:
 On 4/29/14, 3:09 PM, Carl Baldwin
c...@ecbaldwin.netmailto:c...@ecbaldwin.net wrote:I feel this is
an important subject to discuss because the end resultwill be a
better cloud user experience overall.  The design summitcould be a
great time to bring together interested parties fromNeutron, Nova,
and Designate to discuss the integration that I proposein these
blueprints. Do you have a time/location planned for these
discussions? If not, we may have some time in one of the Designate
sessions.  The priorities and details for our design session will be
pulled from 
https://etherpad.openstack.org/p/DesignateAtlantaDesignSession. If you
are interested in joining us, can you add your proposed blueprints in
the format noted there? Thanks, joe
___ OpenStack-dev mailing
list 
OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.o
rg http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev





___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Neutron][Nova][Designate][L3][IPv6] Discussion about Cross-Project Integration of DNS at Summit

2014-05-06 Thread Joe Mcbride

On 4/29/14, 3:09 PM, Carl Baldwin c...@ecbaldwin.net wrote:

I feel this is an important subject to discuss because the end result
will be a better cloud user experience overall.  The design summit
could be a great time to bring together interested parties from
Neutron, Nova, and Designate to discuss the integration that I propose
in these blueprints.

Do you have a time/location planned for these discussions? If not, we may
have some time in one of the Designate sessions.  The priorities and
details for our design session will be pulled from
https://etherpad.openstack.org/p/DesignateAtlantaDesignSession. If you are
interested in joining us, can you add your proposed blueprints in the
format noted there?

Thanks,
joe


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [designate] Summit Design Session Agenda

2014-04-30 Thread Joe Mcbride
I started an etherpad to collect agenda items:
https://etherpad.openstack.org/p/DesignateAtlantaDesignSession

Please add your topics in the described format (requires a blueprint).


Thanks!
Joe McBride
Rackspace


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [designate] FW: Open Source @ OpenStack Submission

2014-04-25 Thread Joe Mcbride
Good news, team.  I’m waiting to hear back on how much time we will be given.

On 4/24/14, 8:58 PM, Chris Hoge 
chris.h...@puppetlabs.commailto:chris.h...@puppetlabs.com wrote:

Dear Graham and Joe,

Thank you for you submission for Designate to the new Open Source @ OpenStack 
program. We're happy to inform you that your developer session was accepted and 
is scheduled for the afternoon of Wednesday, May 14 in room B308. If this time 
works for you, please respond to this e-mail as soon as possible so that we can 
add your session to the official schedule. Once you're confirmed, we will 
follow up with additional resource and session information.

Thanks for your contributions to OpenStack and open source software in general, 
and we look forward to seeing you in Atlanta!

-Chris

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [designate] Workshop dependencies bundled with VM

2014-04-14 Thread Joe Mcbride
Hi guys,
To ensure our workshop is totally untethered and independent of the
interwebs, the VM we plan to distribute should include '.deb' and any
other software dependencies on the VM itself. Can you be sure to keep that
in mind when creating the VM/presentations? An exception can be any docs
or configuration, which can be included on the USB keys.

Thanks,
joe




___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] Designate (DNSaaS) design workshop in Austin, TX

2014-01-20 Thread Joe Mcbride
Greetings,
The Designate project (DNS as a service designed for Openstack) is holding a 
design workshop in Austin TX. 

REGISTER AT:
https://www.eventbrite.com/e/designate-development-workshop-january-2014-tickets-10180041779

WHO SHOULD ATTEND?
- Developers interested in contributing code
- Operators concerned with providing feedback and input into the design process

DATES  TIMES:
All times are Central Standard Time (CST).
- Monday, January 27 from 9:30AM to 5PM
- Tuesday, January 28 from 9:30AM to 5PM
- Wednesday, January 29 from 9:30AM to 2PM

LOCATION:
- The Capital Factory - 701 Brazos St #1601, Austin, TX 78701
- A Google Hangout will also be provided (please register)

AGENDA:
Actual agenda details will be posted later this week. Our workshop priorities 
are:
- Optimize the project software development process
- Blueprint review
- Design sessions
- Team building

MORE WORKSHOP DETAILS:
https://etherpad.openstack.org/p/DesignateAustinWorkshop2014-01


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev