You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@libcloud.apache.org by "Gary Wilson (JIRA)" <ji...@apache.org> on 2012/06/01 19:40:23 UTC
[dev] [jira] [Created] (LIBCLOUD-203) GEO dns record type
Gary Wilson created LIBCLOUD-203:
------------------------------------
Summary: GEO dns record type
Key: LIBCLOUD-203
URL: https://issues.apache.org/jira/browse/LIBCLOUD-203
Project: Libcloud
Issue Type: Improvement
Components: Core
Reporter: Gary Wilson
Add a new dns record type for GEO
It may only be zerigo specific but it is a DNS record type of GEO that is not included in the library. I am guessing it could be added to libcloud/dns/types.py class RecordType as:
GEO = 13
And seeing as the types are not DNS RFC compliant and matched on decimal value that should be OK.
And then a RECORD_TYPE_MAP of GEO in libcloud/dns/drivers/zerigo.py I guess.. I do not know the full complexities of the libcloud framework, debugging and working through it as I go.
If that sounds about right, asign to me and I will patch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[dev] [jira] [Updated] (LIBCLOUD-203) GEO dns record type
Posted by "Gary Wilson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Wilson updated LIBCLOUD-203:
---------------------------------
Attachment: LIBCLOUD-203.patch
Adding DNS Record Type of GEO for dns.zerigo
> GEO dns record type
> -------------------
>
> Key: LIBCLOUD-203
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-203
> Project: Libcloud
> Issue Type: Improvement
> Components: Core
> Reporter: Gary Wilson
> Labels: GEO, RecordType, dns, zerigo
> Attachments: LIBCLOUD-203.patch, LIBCLOUD-203.patch
>
>
> Add a new dns record type for GEO
> It may only be zerigo specific but it is a DNS record type of GEO that is not included in the library. I am guessing it could be added to libcloud/dns/types.py class RecordType as:
> GEO = 13
> And seeing as the types are not DNS RFC compliant and matched on decimal value that should be OK.
> And then a RECORD_TYPE_MAP of GEO in libcloud/dns/drivers/zerigo.py I guess.. I do not know the full complexities of the libcloud framework, debugging and working through it as I go.
> If that sounds about right, asign to me and I will patch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[dev] [jira] [Resolved] (LIBCLOUD-203) GEO dns record type
Posted by "Tomaz Muraus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomaz Muraus resolved LIBCLOUD-203.
-----------------------------------
Resolution: Fixed
Merged into trunk, thanks.
> GEO dns record type
> -------------------
>
> Key: LIBCLOUD-203
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-203
> Project: Libcloud
> Issue Type: Improvement
> Components: Core
> Reporter: Gary Wilson
> Labels: GEO, RecordType, dns, zerigo
> Attachments: LIBCLOUD-203.patch, LIBCLOUD-203.patch
>
>
> Add a new dns record type for GEO
> It may only be zerigo specific but it is a DNS record type of GEO that is not included in the library. I am guessing it could be added to libcloud/dns/types.py class RecordType as:
> GEO = 13
> And seeing as the types are not DNS RFC compliant and matched on decimal value that should be OK.
> And then a RECORD_TYPE_MAP of GEO in libcloud/dns/drivers/zerigo.py I guess.. I do not know the full complexities of the libcloud framework, debugging and working through it as I go.
> If that sounds about right, asign to me and I will patch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[dev] [jira] [Commented] (LIBCLOUD-203) GEO dns record type
Posted by "Gary Wilson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287647#comment-13287647 ]
Gary Wilson commented on LIBCLOUD-203:
--------------------------------------
No worries, happy to be able to contribute.
> GEO dns record type
> -------------------
>
> Key: LIBCLOUD-203
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-203
> Project: Libcloud
> Issue Type: Improvement
> Components: Core
> Reporter: Gary Wilson
> Labels: GEO, RecordType, dns, zerigo
> Attachments: LIBCLOUD-203.patch, LIBCLOUD-203.patch
>
>
> Add a new dns record type for GEO
> It may only be zerigo specific but it is a DNS record type of GEO that is not included in the library. I am guessing it could be added to libcloud/dns/types.py class RecordType as:
> GEO = 13
> And seeing as the types are not DNS RFC compliant and matched on decimal value that should be OK.
> And then a RECORD_TYPE_MAP of GEO in libcloud/dns/drivers/zerigo.py I guess.. I do not know the full complexities of the libcloud framework, debugging and working through it as I go.
> If that sounds about right, asign to me and I will patch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[dev] [jira] [Closed] (LIBCLOUD-203) GEO dns record type
Posted by "Tomaz Muraus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomaz Muraus closed LIBCLOUD-203.
---------------------------------
Assignee: Tomaz Muraus
> GEO dns record type
> -------------------
>
> Key: LIBCLOUD-203
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-203
> Project: Libcloud
> Issue Type: Improvement
> Components: Core
> Reporter: Gary Wilson
> Assignee: Tomaz Muraus
> Labels: GEO, RecordType, dns, zerigo
> Fix For: 0.11.0
>
> Attachments: LIBCLOUD-203.patch, LIBCLOUD-203.patch
>
>
> Add a new dns record type for GEO
> It may only be zerigo specific but it is a DNS record type of GEO that is not included in the library. I am guessing it could be added to libcloud/dns/types.py class RecordType as:
> GEO = 13
> And seeing as the types are not DNS RFC compliant and matched on decimal value that should be OK.
> And then a RECORD_TYPE_MAP of GEO in libcloud/dns/drivers/zerigo.py I guess.. I do not know the full complexities of the libcloud framework, debugging and working through it as I go.
> If that sounds about right, asign to me and I will patch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[dev] [jira] [Comment Edited] (LIBCLOUD-203) GEO dns record type
Posted by "Gary Wilson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287604#comment-13287604 ]
Gary Wilson edited comment on LIBCLOUD-203 at 6/1/12 7:15 PM:
--------------------------------------------------------------
Attaching LIBCLOUD-203.patch
All tox OK and coverage tests OK.
I am appending this issue with the how to setup an ubuntu box as a libcloud dev box and have tox and all the stuff set up and all the git commands, etc. Just in case it helps someone else do it quicker.
The following is in textile markup but... should be OK
h2. branch.LIBCLOUD-203
<pre>
# Install tools for libcloud dev
sudo apt-get install python-pip python-dev build-essential
sudo pip install tox
sudo pip install mock
sudo pip install coverage
GITHUB_DIR=/opt/github
git clone https://github.com/apache/libcloud.git
cd $GITHUB_DIR/libcloud
git checkout trunk
git checkout -b LIBCLOUD-203
# Make modifications to code and modify test file (or run tox and figure out what tests fail and then modify as approriate)
# Modified:
# libcloud/dns/types.py
# libcloud/dns/drivers/zerigo.py
# libcloud/tests/dns/drivers/zerigo.py
cd $GITHUB_DIR/libcloud
cp test/secrets.py-dist test/secrets.py
tox
</pre>
h3. tox.results
Note - [TOX] ERROR: InterpreterNotFound: python2.7 type errors are expected as all the pyton versions will not be available.
<pre>
----------------------------------------------------------------------
Ran 1623 tests in 15.624s
OK
_______________________________________________________________________________ [tox testenv:py27] _______________________________________________________________________________
[TOX] ***creating virtualenv py27
[TOX] ERROR: InterpreterNotFound: python2.7
_______________________________________________________________________________ [tox testenv:pypy] _______________________________________________________________________________
[TOX] ***creating virtualenv pypy
[TOX] ERROR: InterpreterNotFound: pypy
_______________________________________________________________________________ [tox testenv:py32] _______________________________________________________________________________
[TOX] ***creating virtualenv py32
[TOX] ERROR: InterpreterNotFound: python3.2
_________________________________________________________________________________ [tox summary] __________________________________________________________________________________
[TOX] ERROR: py25: InterpreterNotFound: python2.5
[TOX] py26: commands succeeded
[TOX] ERROR: py27: InterpreterNotFound: python2.7
[TOX] ERROR: pypy: InterpreterNotFound: pypy
[TOX] ERROR: py32: InterpreterNotFound: python3.2
</pre>
h3. coverage report
<pre>
cd $GITHUB_DIR/libcloud
PYTHONPATH=. python setup.py coverage
</pre>
Output and you can open coverage_html_report/index.html and see how it looks.. :)
<pre>
...
...
Doctest: libcloud.dns.drivers.dummy.DummyDNSDriver.list_record_types ... ok
Doctest: libcloud.dns.drivers.dummy.DummyDNSDriver.list_zones ... ok
----------------------------------------------------------------------
Ran 1623 tests in 13.325s
OK
</pre>
h3. git patch and commit
<pre>
cd $GITHUB_DIR/libcloud
git commit -am "IssueID #203: LIBCLOUD-203
URL: https://issues.apache.org/jira/browse/LIBCLOUD-203
Added new DNS Record Type of GEO
All tox OK
Modified:
libcloud/dns/types.py
libcloud/dns/drivers/zerigo.py
libcloud/tests/dns/drivers/zerigo.py"
git format-patch --no-prefix --stdout trunk > LIBCLOUD-203.patch
git diff --no-prefix trunk LIBCLOUD-203 > LIBCLOUD-203.patch
git push origin LIBCLOUD-203
# Attach patch to LIBCLOUD-203 issue
# And for next time... switch back to trunk..
git checkout trunk
</pre>
was (Author: earthgecko):
Attaching LIBCLOUD-203.patch
All tox OK and coverage tests OK.
I am appending this issue with the how to setup an ubuntu box as a libcloud dev box and have tox and all the stuff set up and all the git commands, etc. Just in case it helps someone else do it quicker.
The following is in textile markup but... should be OK
h2. branch.LIBCLOUD-203
<pre>
# Install tools for libcloud dev
sudo apt-get install python-pip python-dev build-essential
sudo pip install tox
sudo pip install mock
sudo pip install coverage
GITHUB_DIR=/opt/github
git clone https://github.com/apache/libcloud.git
cd $GITHUB_DIR/libcloud
git checkout trunk
git checkout -b LIBCLOUD-203
# Make modifications to code and modify test file (or run tox and figure out what tests fail and then modify as approriate)
# Modified:
# libcloud/dns/types.py
# libcloud/dns/drivers/zerigo.py
# libcloud/tests/dns/drivers/zerigo.py
cd $GITHUB_DIR/libcloud
cp test/secrets.py-dist test/secrets.py
tox
</pre>
h3. tox.results
Note - [TOX] ERROR: InterpreterNotFound: python2.7 type errors are expected as all the pyton versions will not be available.
<pre>
----------------------------------------------------------------------
Ran 1623 tests in 15.624s
OK
_______________________________________________________________________________ [tox testenv:py27] _______________________________________________________________________________
[TOX] ***creating virtualenv py27
[TOX] ERROR: InterpreterNotFound: python2.7
_______________________________________________________________________________ [tox testenv:pypy] _______________________________________________________________________________
[TOX] ***creating virtualenv pypy
[TOX] ERROR: InterpreterNotFound: pypy
_______________________________________________________________________________ [tox testenv:py32] _______________________________________________________________________________
[TOX] ***creating virtualenv py32
[TOX] ERROR: InterpreterNotFound: python3.2
_________________________________________________________________________________ [tox summary] __________________________________________________________________________________
[TOX] ERROR: py25: InterpreterNotFound: python2.5
[TOX] py26: commands succeeded
[TOX] ERROR: py27: InterpreterNotFound: python2.7
[TOX] ERROR: pypy: InterpreterNotFound: pypy
[TOX] ERROR: py32: InterpreterNotFound: python3.2
</pre>
h3. coverage report
<pre>
cd $GITHUB_DIR/libcloud
PYTHONPATH=. python setup.py coverage
</pre>
Output and you can open coverage_html_report/index.html and see how it looks.. :)
<pre>
...
...
Doctest: libcloud.dns.drivers.dummy.DummyDNSDriver.list_record_types ... ok
Doctest: libcloud.dns.drivers.dummy.DummyDNSDriver.list_zones ... ok
----------------------------------------------------------------------
Ran 1623 tests in 13.325s
OK
</pre>
h3. git patch and commit
<pre>
cd $GITHUB_DIR/libcloud
git commit -am "IssueID #203: LIBCLOUD-203
URL: https://issues.apache.org/jira/browse/LIBCLOUD-203
Added new DNS Record Type of GEO
All tox OK
Modified:
libcloud/dns/types.py
libcloud/dns/drivers/zerigo.py
libcloud/tests/dns/drivers/zerigo.py"
git push origin LIBCLOUD-203
# Attach patch to LIBCLOUD-203 issue
# And for next time... switch back to trunk..
git checkout trunk
</pre>
> GEO dns record type
> -------------------
>
> Key: LIBCLOUD-203
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-203
> Project: Libcloud
> Issue Type: Improvement
> Components: Core
> Reporter: Gary Wilson
> Labels: GEO, RecordType, dns, zerigo
> Attachments: LIBCLOUD-203.patch, LIBCLOUD-203.patch
>
>
> Add a new dns record type for GEO
> It may only be zerigo specific but it is a DNS record type of GEO that is not included in the library. I am guessing it could be added to libcloud/dns/types.py class RecordType as:
> GEO = 13
> And seeing as the types are not DNS RFC compliant and matched on decimal value that should be OK.
> And then a RECORD_TYPE_MAP of GEO in libcloud/dns/drivers/zerigo.py I guess.. I do not know the full complexities of the libcloud framework, debugging and working through it as I go.
> If that sounds about right, asign to me and I will patch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[dev] [jira] [Updated] (LIBCLOUD-203) GEO dns record type
Posted by "Tomaz Muraus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomaz Muraus updated LIBCLOUD-203:
----------------------------------
Fix Version/s: 0.11.0
> GEO dns record type
> -------------------
>
> Key: LIBCLOUD-203
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-203
> Project: Libcloud
> Issue Type: Improvement
> Components: Core
> Reporter: Gary Wilson
> Labels: GEO, RecordType, dns, zerigo
> Fix For: 0.11.0
>
> Attachments: LIBCLOUD-203.patch, LIBCLOUD-203.patch
>
>
> Add a new dns record type for GEO
> It may only be zerigo specific but it is a DNS record type of GEO that is not included in the library. I am guessing it could be added to libcloud/dns/types.py class RecordType as:
> GEO = 13
> And seeing as the types are not DNS RFC compliant and matched on decimal value that should be OK.
> And then a RECORD_TYPE_MAP of GEO in libcloud/dns/drivers/zerigo.py I guess.. I do not know the full complexities of the libcloud framework, debugging and working through it as I go.
> If that sounds about right, asign to me and I will patch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[dev] [jira] [Commented] (LIBCLOUD-203) GEO dns record type
Posted by "Tomaz Muraus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287562#comment-13287562 ]
Tomaz Muraus commented on LIBCLOUD-203:
---------------------------------------
Yeah, that sounds correct. Add it to RecordType class / enum and then update RECORD_TYPE_MAP in the zerigo driver. Also don't forget to add tests.
> GEO dns record type
> -------------------
>
> Key: LIBCLOUD-203
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-203
> Project: Libcloud
> Issue Type: Improvement
> Components: Core
> Reporter: Gary Wilson
> Labels: GEO, RecordType, dns, zerigo
>
> Add a new dns record type for GEO
> It may only be zerigo specific but it is a DNS record type of GEO that is not included in the library. I am guessing it could be added to libcloud/dns/types.py class RecordType as:
> GEO = 13
> And seeing as the types are not DNS RFC compliant and matched on decimal value that should be OK.
> And then a RECORD_TYPE_MAP of GEO in libcloud/dns/drivers/zerigo.py I guess.. I do not know the full complexities of the libcloud framework, debugging and working through it as I go.
> If that sounds about right, asign to me and I will patch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[dev] [jira] [Updated] (LIBCLOUD-203) GEO dns record type
Posted by "Gary Wilson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Wilson updated LIBCLOUD-203:
---------------------------------
Attachment: LIBCLOUD-203.patch
Adding a new DNS Record Type - GEO
> GEO dns record type
> -------------------
>
> Key: LIBCLOUD-203
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-203
> Project: Libcloud
> Issue Type: Improvement
> Components: Core
> Reporter: Gary Wilson
> Labels: GEO, RecordType, dns, zerigo
> Attachments: LIBCLOUD-203.patch, LIBCLOUD-203.patch
>
>
> Add a new dns record type for GEO
> It may only be zerigo specific but it is a DNS record type of GEO that is not included in the library. I am guessing it could be added to libcloud/dns/types.py class RecordType as:
> GEO = 13
> And seeing as the types are not DNS RFC compliant and matched on decimal value that should be OK.
> And then a RECORD_TYPE_MAP of GEO in libcloud/dns/drivers/zerigo.py I guess.. I do not know the full complexities of the libcloud framework, debugging and working through it as I go.
> If that sounds about right, asign to me and I will patch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[dev] [jira] [Commented] (LIBCLOUD-203) GEO dns record type
Posted by "Gary Wilson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287604#comment-13287604 ]
Gary Wilson commented on LIBCLOUD-203:
--------------------------------------
Attaching LIBCLOUD-203.patch
All tox OK and coverage tests OK.
I am appending this issue with the how to setup an ubuntu box as a libcloud dev box and have tox and all the stuff set up and all the git commands, etc. Just in case it helps someone else do it quicker.
The following is in textile markup but... should be OK
h2. branch.LIBCLOUD-203
<pre>
# Install tools for libcloud dev
sudo apt-get install python-pip python-dev build-essential
sudo pip install tox
sudo pip install mock
sudo pip install coverage
GITHUB_DIR=/opt/github
git clone https://github.com/apache/libcloud.git
cd $GITHUB_DIR/libcloud
git checkout trunk
git checkout -b LIBCLOUD-203
# Make modifications to code and modify test file (or run tox and figure out what tests fail and then modify as approriate)
# Modified:
# libcloud/dns/types.py
# libcloud/dns/drivers/zerigo.py
# libcloud/tests/dns/drivers/zerigo.py
cd $GITHUB_DIR/libcloud
cp test/secrets.py-dist test/secrets.py
tox
</pre>
h3. tox.results
Note - [TOX] ERROR: InterpreterNotFound: python2.7 type errors are expected as all the pyton versions will not be available.
<pre>
----------------------------------------------------------------------
Ran 1623 tests in 15.624s
OK
_______________________________________________________________________________ [tox testenv:py27] _______________________________________________________________________________
[TOX] ***creating virtualenv py27
[TOX] ERROR: InterpreterNotFound: python2.7
_______________________________________________________________________________ [tox testenv:pypy] _______________________________________________________________________________
[TOX] ***creating virtualenv pypy
[TOX] ERROR: InterpreterNotFound: pypy
_______________________________________________________________________________ [tox testenv:py32] _______________________________________________________________________________
[TOX] ***creating virtualenv py32
[TOX] ERROR: InterpreterNotFound: python3.2
_________________________________________________________________________________ [tox summary] __________________________________________________________________________________
[TOX] ERROR: py25: InterpreterNotFound: python2.5
[TOX] py26: commands succeeded
[TOX] ERROR: py27: InterpreterNotFound: python2.7
[TOX] ERROR: pypy: InterpreterNotFound: pypy
[TOX] ERROR: py32: InterpreterNotFound: python3.2
</pre>
h3. coverage report
<pre>
cd $GITHUB_DIR/libcloud
PYTHONPATH=. python setup.py coverage
</pre>
Output and you can open coverage_html_report/index.html and see how it looks.. :)
<pre>
...
...
Doctest: libcloud.dns.drivers.dummy.DummyDNSDriver.list_record_types ... ok
Doctest: libcloud.dns.drivers.dummy.DummyDNSDriver.list_zones ... ok
----------------------------------------------------------------------
Ran 1623 tests in 13.325s
OK
</pre>
h3. git patch and commit
<pre>
cd $GITHUB_DIR/libcloud
git commit -am "IssueID #203: LIBCLOUD-203
URL: https://issues.apache.org/jira/browse/LIBCLOUD-203
Added new DNS Record Type of GEO
All tox OK
Modified:
libcloud/dns/types.py
libcloud/dns/drivers/zerigo.py
libcloud/tests/dns/drivers/zerigo.py"
git push origin LIBCLOUD-203
# Attach patch to LIBCLOUD-203 issue
# And for next time... switch back to trunk..
git checkout trunk
</pre>
> GEO dns record type
> -------------------
>
> Key: LIBCLOUD-203
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-203
> Project: Libcloud
> Issue Type: Improvement
> Components: Core
> Reporter: Gary Wilson
> Labels: GEO, RecordType, dns, zerigo
> Attachments: LIBCLOUD-203.patch, LIBCLOUD-203.patch
>
>
> Add a new dns record type for GEO
> It may only be zerigo specific but it is a DNS record type of GEO that is not included in the library. I am guessing it could be added to libcloud/dns/types.py class RecordType as:
> GEO = 13
> And seeing as the types are not DNS RFC compliant and matched on decimal value that should be OK.
> And then a RECORD_TYPE_MAP of GEO in libcloud/dns/drivers/zerigo.py I guess.. I do not know the full complexities of the libcloud framework, debugging and working through it as I go.
> If that sounds about right, asign to me and I will patch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira