Change last of the URLs from stackforge to openstack

Change stackforge to openstack. Fix a couple of typos in the
rest of the URLs as well

Change-Id: I9ac209e0d891b78d445d298485c8ce4484781493

README.md

@@ -30,13 +30,13 @@ For an introduction to the Monasca Agent, including a complete list of the metri
 
 The Agent is extensible through configuration of additional check and setup plugins, written in Python. See the "Agent Customizations" detailed documentation.
 
-Agent [github.com/stackforge/monasca-agent/blob/master/docs/Agent.md](https://github.com/stackforge/monasca-agent/blob/master/docs/Agent.md)
+Agent [github.com/openstack/monasca-agent/blob/master/docs/Agent.md](https://github.com/openstack/monasca-agent/blob/master/docs/Agent.md)
 
-Agent Customizations [github.com/stackforge/monasca-agent/docs/Customizations.md](https://github.com/stackforge/monasca-agent/blob/master/docs/Customizations.md)
+Agent Customizations [github.com/openstack/monasca-agent/docs/Customizations.md](https://github.com/openstack/monasca-agent/blob/master/docs/Customizations.md)
 
-Monasca Metrics [github.com/stackforge/monasca-agent/docs/MonascaMetrics.md](https://github.com/stackforge/monasca-agent/blob/master/docs/MonascaMetrics.md)
+Monasca Metrics [github.com/openstack/monasca-agent/docs/MonascaMetrics.md](https://github.com/openstack/monasca-agent/blob/master/docs/MonascaMetrics.md)
 
-Agent Plugin details [github.com/stackforge/monasca-agent/docs/Plugins.md](https://github.com/stackforge/monasca-agent/blob/master/docs/Plugins.md)
+Agent Plugin details [github.com/openstack/monasca-agent/docs/Plugins.md](https://github.com/openstack/monasca-agent/blob/master/docs/Plugins.md)
 
 # License
 Copyright (c) 2015 Hewlett-Packard Development Company, L.P.

conf.d/http_check.yaml.example

@@ -14,7 +14,7 @@ instances:
          # specify the information to collect a token to be used in the check.
          # This information should follow the same guidelines presented in
          # agent.yaml.template
-         # https://github.com/stackforge/monasca-agent/blob/master/agent.yaml.template
+         # https://github.com/openstack/monasca-agent/blob/master/agent.yaml.template
          # If use_keystone=True and keystone_config is not specified, the keystone information
          # from the agent config will be used.
 #        use_keystone: True

conf.d/http_metrics.yaml.example

@@ -14,7 +14,7 @@ instances:
          # specify the information to collect a token to be used in the check.
          # This information should follow the same guidelines presented in
          # agent.yaml.template
-         # https://github.com/stackforge/monasca-agent/blob/master/agent.yaml.template
+         # https://github.com/openstack/monasca-agent/blob/master/agent.yaml.template
          # If use_keystone=True and keystone_config is not specified, the keystone information
          # from the agent config will be used.
 #        use_keystone=True

docs/Agent.md

@@ -21,7 +21,7 @@ The Monasca Agent is the component of the [Monasca](https://wiki.openstack.org/w
 
 A metric is identified by a name and dimensions.  The fields required in a metric are name, timestamp, and value.  A metric can also have 0..n dimensions.  Some standard dimensions are sent with all metrics that are sent by the agent.
 
-<img src="https://github.com/stackforge/monasca-agent/raw/master/docs/monasca-agent_arch.png" alt="Monasca Agent Diagram">
+<img src="https://github.com/openstack/monasca-agent/raw/master/docs/monasca-agent_arch.png" alt="Monasca Agent Diagram">
 
 The flow of the agent application goes like this:
 

docs/Customizations.md

@@ -56,7 +56,7 @@ The built-in Python check plugin scripts are installed as part of the monasca-ag
 
 Config files for the plugin scripts can be added directly to the standard plugin configuration directory, `/etc/monasca/agent/conf.d` or added by a `monasca-setup` plugin script that auto-detects that the checks are required and then generates and adds the appropriate config file to enable them.
 
-See [Plugin Checks](#https://github.com/stackforge/monasca-agent/blob/master/docs/Plugins) for a description of the configuration and output of the built-in check plugins.
+See [Plugin Checks](#https://github.com/openstack/monasca-agent/blob/master/docs/Plugins.md#standard-plugins) for a description of the configuration and output of the built-in check plugins.
 
 ### Adding Custom Check Plugins
 
@@ -97,7 +97,7 @@ Be aware of these best practices before defining new metrics and adding custom p
 
 Here are some best practices concerning appropriate use of metrics:
 
-- Be aware of [naming conventions](#https://github.com/stackforge/monasca-agent/blob/master/docs/MonascaMetrics.md) with metrics.
+- Be aware of [naming conventions](#https://github.com/openstack/monasca-agent/blob/master/docs/MonascaMetrics.md) with metrics.
 - Considerations affecting system performance
   - Before installing and configuring a custom check plugin, be certain that you have identified consumers who will actually make use of the metric.
   - Before defining a new metric, make sure that a metric that is essentially the same hasn't already been defined. If it has, use that definition. Re-use is good!
@@ -107,7 +107,7 @@ Here are some best practices concerning appropriate use of metrics:
 
 ### Custom Plugin Best Practices
 
-- Before creating a custom plugin, see if your needs can be met by an existing plugin (See [Plugin Checks](#https://github.com/stackforge/monasca-agent/blob/master/README.md#plugin-checks) for a list of them.)
+- Before creating a custom plugin, see if your needs can be met by an existing plugin (See [Plugin Checks](#https://github.com/openstack/monasca-agent/blob/master/docs/Plugins.md#standard-plugins) for a list of them.)
 - If you identify a bug or other problem with an existing plugin, report the defect so everyone can benefit from your discovery.
 - If you do create custom plugins, consider upstreaming them if you think others would benefit from using them.
 - When writing your plugins, strive for efficiency and economy. Have the plugin perform the necessary checks in the most efficient way. Remember that cycles spent monitoring the system are cycles that cannot be used by the "application" components running on the system.
@@ -115,7 +115,7 @@ Here are some best practices concerning appropriate use of metrics:
 
 ## Creating Custom Plugins
 
-The references in these sections to classes, utilities, etc. are to locations in the monasca-agent git repo, `https://github.com/stackforge/monasca-agent`.
+The references in these sections to classes, utilities, etc. are to locations in the monasca-agent git repo, `https://git.openstack.org/openstack/monasca-agent`.
 
 ### Creating a Custom Check Plugin
 

docs/MonascaMetrics.md

@@ -126,7 +126,7 @@ Once the Agent's user and project are assigned to the `monitoring-delegate` grou
 # Statsd
 The Monasca Agent ships with a Statsd daemon implementation called monasca-statsd. A statsd client can be used to send metrics to the Forwarder via the Statsd daemon.
 
-monasca-statsd will accept metrics submitted by functions in either the standard statsd Python client library, or the monasca-agent's [monasca-statsd Python client library](https://github.com/stackforge/monasca-statsd). The advantage of using the python-monasca-statsd library is that it is possible to specify dimensions on submitted metrics. Dimensions are not handled by the standard statsd client.
+monasca-statsd will accept metrics submitted by functions in either the standard statsd Python client library, or the monasca-agent's [monasca-statsd Python client library](https://github.com/openstack/monasca-statsd). The advantage of using the python-monasca-statsd library is that it is possible to specify dimensions on submitted metrics. Dimensions are not handled by the standard statsd client.
 
 Statsd metrics are not bundled along with the metrics gathered by the Collector, but are flushed to the agent Forwarder on a separate schedule (every 10 seconds by default, rather than 60 seconds for Collector metrics).
 
@@ -140,7 +140,7 @@ statsd.timing('pipeline', 2468.34)      # Pipeline took 2468.34 ms to execute
 statsd.gauge('gaugething', 3.14159265)  # 'gauge' would be the preferred metric type for Monitoring
 ```
 
-The [monasca-statsd](https://github.com/stackforge/monasca-statsd library provides a python based implementation of a statsd client but also adds the ability to add dimensions to the the statsd metrics for the client.
+The [monasca-statsd](https://github.com/openstack/monasca-statsd library provides a python based implementation of a statsd client but also adds the ability to add dimensions to the the statsd metrics for the client.
 
 Here are some examples of how code can be instrumented using calls to monasca-statsd.
 ```

docs/Plugins.md

@@ -1006,7 +1006,7 @@ In order to fetch data on hosted compute instances, the Libvirt plugin needs to
 
 The Libvirt plugin uses a cache directory to persist data, which is `/dev/shm` by default.  On non-Linux systems (BSD, Mac OSX), `/dev/shm` may not exist, so `cache_dir` would need to be changed accordingly, either in `monasca_setup/detection/plugins/libvirt.py` prior to running `monasca-setup`, or `/etc/monasca/agent/conf.d/libvirt.yaml` afterwards.
 
-If the owner of the VM is in a different tenant the Agent Cross-Tenant Metric Submission can be setup. See this [documentation](https://github.com/stackforge/monasca-agent/blob/master/docs/MonascaMetrics.md#cross-tenant-metric-submission) for details.
+If the owner of the VM is in a different tenant the Agent Cross-Tenant Metric Submission can be setup. See this [documentation](https://github.com/openstack/monasca-agent/blob/master/docs/MonascaMetrics.md#cross-tenant-metric-submission) for details.
 
 `nova_refresh` specifies the number of seconds between calls to the Nova API to refresh the instance cache.  This is helpful for updating VM hostname and pruning deleted instances from the cache.  By default, it is set to 14,400 seconds (four hours).  Set to 0 to refresh every time the Collector runs, or to None to disable regular refreshes entirely (though the instance cache will still be refreshed if a new instance is detected).
 

docs/index.md

@@ -1,6 +1,6 @@
 # Monasca Agent Documentation
 
-Please refer to the [project readme](https://github.com/stackforge/monasca-agent) for Agent documentation.
+Please refer to the [project readme](https://github.com/openstack/monasca-agent) for Agent documentation.
 
 For full Monasca documentation visit [wiki.openstack.org/wiki/Monasca](https://wiki.openstack.org/wiki/Monasca)
 
@@ -21,7 +21,7 @@ For full Monasca documentation visit [wiki.openstack.org/wiki/Monasca](https://w
 
     ##### Edit the mkdocs yaml
     site_name: monasca-agent
-    repo_url: https://github.com/stackforge/monasca-agent
+    repo_url: https://github.com/openstack/monasca-agent
 
     ##### Move the existing README.md
     mv README.md docs

mkdocs.yml

@@ -1,5 +1,5 @@
 site_name: monasca-agent
-repo_url: https://github.com/stackforge/monasca-agent
+repo_url: https://github.com/openstack/monasca-agent
 docs_dir: docs
 copyright: Copyright (c) 2015 Hewlett-Packard Development Company, L.P.
 

setup.cfg

@@ -3,7 +3,7 @@ name=monasca-agent
 maintainer=monasca
 maintainer_email=monasca@lists.launchpad.net
 description-file = README.md
-home-page = https://github.com/stackforge/monasca-agent
+home-page = https://github.com/openstack/monasca-agent
 keywords=
     openstack
     monitoring