Infrastructure
  1. Infrastructure
  2. INFRA-5195

Create a planet instance to host http://planet.cloudstack.**.apache.org

    Details

      Description

      Greetings. The CloudStack community would like to set up a "planet" blog aggregator. Due to one of our goals of allowing feeds from non-committers, we intend to point planet.cloudstack.org to the server, so as to not use the apache.org namespace.

      Based off an irc descussion in #asfinfra last week, we'd like to host this in a VM on ASF infrastructure. We held a VOTE on the topic to move forward in this direction. The results (+7) are in the email thread at the URL below.

      http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201208.mbox/%3C348B2883-E8A4-4B99-AC3E-BEF2ACD63D3A%40stratosec.co%3E

      Happy to provide any additional details that are needed.

        Activity

        Hide
        #asfinfra IRC Bot added a comment -
        <danielsh> 1) not sure whether "not on apache.org" is implied by "non-committers content" so long as the PMC monitors / invites the content; may want to ask on trademarks@ or some other org-wide list. 2) why a VM? can't this be installed as an infra service? or do you want to maintain it, install custom plugins, etc ?
        Show
        #asfinfra IRC Bot added a comment - <danielsh> 1) not sure whether "not on apache.org" is implied by "non-committers content" so long as the PMC monitors / invites the content; may want to ask on trademarks@ or some other org-wide list. 2) why a VM? can't this be installed as an infra service? or do you want to maintain it, install custom plugins, etc ?
        Hide
        John Kinsella added a comment -
        1) The previous discussion made it sound like "non-committers content" was implying "not on apache.org" but I'll reach out to trademarks@ for comment. Will update this ticket once I see useful feedback.

        2) installing as a infra service is fine with us - the less custom maintenance that's required, the better. Apologies, I'm still learning the Apache Way for a lot of these things. In general, presume I'm looking for the most efficient, most logical path forward.
        Show
        John Kinsella added a comment - 1) The previous discussion made it sound like "non-committers content" was implying "not on apache.org" but I'll reach out to trademarks@ for comment. Will update this ticket once I see useful feedback. 2) installing as a infra service is fine with us - the less custom maintenance that's required, the better. Apologies, I'm still learning the Apache Way for a lot of these things. In general, presume I'm looking for the most efficient, most logical path forward.
        Hide
        #asfinfra IRC Bot added a comment -
        <danielsh> The most $adjective path forward depends on your requirements. What kind of access do you need to the service? Just the ability to add/remove feeds (cf how planet.ini works today), or something beyond that?
        Show
        #asfinfra IRC Bot added a comment - <danielsh> The most $adjective path forward depends on your requirements. What kind of access do you need to the service? Just the ability to add/remove feeds (cf how planet.ini works today), or something beyond that?
        Hide
        #asfinfra IRC Bot added a comment -
        <danielsh> <jlkinsel> yes
        Show
        #asfinfra IRC Bot added a comment - <danielsh> <jlkinsel> yes
        Hide
        #asfinfra IRC Bot added a comment -
        <danielsh> Guys, can you please provide the location in svn that will hold the config files for your instance? (It's ok if there is only minimal content for now, just something we can use once we get around to handling this ticket.)
        Show
        #asfinfra IRC Bot added a comment - <danielsh> Guys, can you please provide the location in svn that will hold the config files for your instance? (It's ok if there is only minimal content for now, just something we can use once we get around to handling this ticket.)
        Hide
        John Kinsella added a comment -
        Sorry guys - lost track of this and then got busy.

        Just checked in /repos/asf/incubator/cloudstack/planet/trunk/planet-cloudstack.ini - can we give that a try?
        Show
        John Kinsella added a comment - Sorry guys - lost track of this and then got busy. Just checked in /repos/asf/incubator/cloudstack/planet/trunk/planet-cloudstack.ini - can we give that a try?
        Show
        #asfinfra IRC Bot added a comment - <danielsh> https://svn.apache.org/repos/asf/incubator/cloudstack/planet/trunk/planet-cloudstack.ini
        Hide
        #asfinfra IRC Bot added a comment -
        <danielsh> This will be set up on an *.apache.org domain; please contact trademarks@ for details.
        Show
        #asfinfra IRC Bot added a comment - <danielsh> This will be set up on an *.apache.org domain; please contact trademarks@ for details.
        Hide
        Shane Curcuru added a comment -
        Apache project services generally must be hosted on an *.apache.org domain. This is a key part of branding for all Apache projects. Thus hosting a service on a cloudstack.org URL is not appropriate.

        Note that in limited cases - where there is already a long-running and highly-linked to URL from the previous project name - it should be OK to use those as a bridge for current URL cards/tweets/etc., presuming that the URLs provide a Redirect Permanent or the like to the appropriate underlying *.apache.org service. We certainly don't need to cause branding pain up front, but in the long term, projects live on *.apache.org for all official services.
        Show
        Shane Curcuru added a comment - Apache project services generally must be hosted on an *.apache.org domain. This is a key part of branding for all Apache projects. Thus hosting a service on a cloudstack.org URL is not appropriate. Note that in limited cases - where there is already a long-running and highly-linked to URL from the previous project name - it should be OK to use those as a bridge for current URL cards/tweets/etc., presuming that the URLs provide a Redirect Permanent or the like to the appropriate underlying *.apache.org service. We certainly don't need to cause branding pain up front, but in the long term, projects live on *.apache.org for all official services.
        Hide
        John Kinsella added a comment -
        Shane - thanks for the comments.

        So - is it OK for us to put a blog aggregator at http://planet.apache.org/cloudstack, with content from both committers and approved non-committers?
        Show
        John Kinsella added a comment - Shane - thanks for the comments. So - is it OK for us to put a blog aggregator at http://planet.apache.org/cloudstack, with content from both committers and approved non-committers?
        Hide
        #asfinfra IRC Bot added a comment -
        <danielsh> It's in the queue John, whoever works on this issue will figure out the exact domain name
        Show
        #asfinfra IRC Bot added a comment - <danielsh> It's in the queue John, whoever works on this issue will figure out the exact domain name
        Hide
        John Kinsella added a comment -
        My bad about posting the private email, I do know better. Deleted. Sorry again for slow response, been out on family emergency.
        Show
        John Kinsella added a comment - My bad about posting the private email, I do know better. Deleted. Sorry again for slow response, been out on family emergency.
        Hide
        #asfinfra IRC Bot added a comment -
        <danielsh> Thanks, and all the best to your family
        Show
        #asfinfra IRC Bot added a comment - <danielsh> Thanks, and all the best to your family
        Hide
        John Kinsella added a comment -
        Hey guys, happy new year - just looking to give this a gentle nudge...

        To recap, what we're looking for is to have venus aggregate CloudStack blogs at http://planet.apache.org/cloudstack, with the config file found at https://svn.apache.org/repos/asf/incubator/cloudstack/planet/trunk/planet-cloudstack.ini.

        If I can help in any way, lemme know.
        Show
        John Kinsella added a comment - Hey guys, happy new year - just looking to give this a gentle nudge... To recap, what we're looking for is to have venus aggregate CloudStack blogs at http://planet.apache.org/cloudstack, with the config file found at https://svn.apache.org/repos/asf/incubator/cloudstack/planet/trunk/planet-cloudstack.ini . If I can help in any way, lemme know.
        Hide
        Tony Stevenson added a comment -
        I have now got this working for you.

        http://planet.apache.org/cloudstack/

        However to make this easier, I have had to move the config from the CS repo, to the main planet repo. You can now find this here - http://svn.apache.org/repos/asf/planet/cloudstack.ini

        This will apply automatically, every 5 minutes. So it needs to be syntactically correct or it will break the config, and thus the update. This will need a member of root@ to fix it in this case.
        Show
        Tony Stevenson added a comment - I have now got this working for you. http://planet.apache.org/cloudstack/ However to make this easier, I have had to move the config from the CS repo, to the main planet repo. You can now find this here - http://svn.apache.org/repos/asf/planet/cloudstack.ini This will apply automatically, every 5 minutes. So it needs to be syntactically correct or it will break the config, and thus the update. This will need a member of root@ to fix it in this case.

          People

          • Assignee:
            Tony Stevenson
            Reporter:
            John Kinsella
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development