When I try to "Update network topology from ghost nodes" using the Australian bureau of meteorology 'geofabric', the upated layer does not add any ghost nodes from my database.
I have checked the ghost node database to make sure all the feature classes are correct.
Related
Currently, I got a task about integrating ECS openshift with AppDynamics.
Here is my situation, I have Integrated my project with AppDynamics . I can’t see my project on appDynamics Dashboard, but I can see it on the Tier and node. i have checked the router for openshift,it’s not available ，so i want to ask you guys if it is the reason why i can not see my project on the AppDynamics Dashboard ？
If your Nodes are showing under "Tiers & Nodes" this means that the Agents are reporting to the AppDynamics Controller.
If however there is nothing shown in the Application (or Tier, or Node) Dashboards this means that there are no registered Business Transactions relating to that Application (or Tier, or Node).
Dashboards (or flow maps, more accurately) generally show a view of registered Business Transactions (not simply of entities which are known to the Controller).
Have a look at the docs for an explanation of what a Business Transaction is and how these can be configured should none be detected OOTB:
https://docs.appdynamics.com/21.2/en/application-monitoring/configure-instrumentation/transaction-detection-rules
https://docs.appdynamics.com/21.2/en/application-monitoring/business-transactions
Hi I am a new learner here, and going through the docs in cloud foundry and not able to find much like how Cloud Foundry is able to scale so quickly?
What is there in back which makes it so fast and easy to scale?
I have worked with Pivotal Cloud Foundry and will try to explain concepts with it.
Here is the link to the Diego Architecture.
Please look closely to the architecture diagram.
The diagram depicts the components within PCF and how they interact.
Cloud Foundry is an ecosystem containing a lot of components. The cells in the diagram are the Diego Cells. These are the actual vm's where containers are hosted and run.
At basic level, containers are in-fact folders on a host VM, with runtime isolations. A container does not know anything about another container.
When you push an app to PCF, the first thing that happens is the app is staged. Here is an article explaining How Diego Stages Buildpack Applications.
Notice the Blobstore. As part of the staging process, the cloud controller uploads a ready-to-go blob to the Blobstore. This blob contains, the OS, monitoring tools (both sourced from stem cell), the runtime (jvm, api tools etc from buildpack), and your application archive.
Cloud Foundry runs one and only one application in a container. That is very important. If the app dies, the container is reclaimed. A new container will spun up in its place.
A spinning up a brand new VM is expensive in terms of time and resources. Spinning up a new container on an existing VM is relatively very cheap. And, PCF has a ready-to-go blob available.
So, if there is a need to scale up or if an app instance crashes, PCF will be able to spin a new instance.
There are a ton of things involved in this process. The articles will walk you through it.
Hope this helps.
I'm trying to run a network analysis and was wondering if there was a way to have the service area facilities as polygons instead of points?
I've tried the feature to point tool but this create one point which doesn't account for the whole area of the polygon.
Is there a tool that creates multiple points that outline the polygon?
I'll try to answer the first paragraph (I am not sure I fully understand connection with the second part).
Besides buffers, readily available in ArcMap, with an ArcGIS Desktop extension one can crate Drive Time polygons around point features:
With Business Analyst extension, Drive Time polygons can be created using the eponymous tool:
http://desktop.arcgis.com/en/arcmap/latest/tools/business-analyst-toolbox/drive-time.htm
As they state,
You can create more advanced drive-time polygons with custom road
networks, adding barriers, and the like with the ArcGIS Network
Analyst tools
With Network Analyst extension, Make Service Area Layer tool is available:
http://desktop.arcgis.com/en/arcmap/latest/tools/network-analyst-toolbox/make-service-area-layer.htm
After creating the analysis layer with this tool, you can add network
analysis objects to it using the Add Locations tool, solve the
analysis using the Solve tool, and save the results on disk using the
Save To Layer File tool.
With Network Analyst extension, Generate Service Areas could be used for setting up a service areas Geoprocessing service:
http://desktop.arcgis.com/en/arcmap/latest/tools/network-analyst-toolbox/generate-service-areas.htm
Creates a service area network analysis layer, sets the analysis
properties, and solves the analysis. This tool is ideal for setting up
a service area geoprocessing service on the web. A network service
area is a region that encompasses all streets that can be accessed
within a given distance or travel time from one or more facilities.
Example:
http://server.arcgis.com/en/server/latest/publish-services/windows/gp-service-example-drivetime-polygons.htm
With an an ArcGIS Online for organizations account, one can consume a ready to go service:
http://desktop.arcgis.com/en/arcmap/latest/extensions/network-analyst/itemdesc-generate-service-areas.htm
It is a service that runs like a geoprocessing tool within ArcMap, can
be accessed from other applications, and includes high-quality road
data for much of the world.
UPDATE:
From ArcGIS Online Help (see the Examples section):
http://doc.arcgis.com/en/arcgis-online/analyze/create-drive-time-areas.htm
I'm looking for a scaling mechanism on OpenStack cloud, and then I found OpenShift. My scenario is something like this: we have a distributed system with many agents stand on many nodes. One node contain a Message Broker that direct the traffic. We want to monitor the Message Broker node, if a queue is full, we scale out the agent nodes handle that queue. In brief, we monitor one node to scale other nodes.
We used OpenStack cloud now. In OpenStack, I found heat and ceilometer which are able to create alarm and scale out nodes. However, alarms are based only on general info like CPU, RAM, Network usage, etc (not inside-VM info).
Then I search for a layer above: PaaS. I found OpenShift can handle scaling apps. But as I knew, the scaling mechanism of OpenShift is: duplicate the apps based on network traffic, then put an HAProxy in front.
Am I right that OpenShift can't monitor software specific data. Is there any other tool that suit our scenario?
You can try using this script (https://github.com/openshift/origin-server/blob/master/cartridges/openshift-origin-cartridge-haproxy/usr/bin/haproxy_ctld.rb) to control how your gears are scaled, but I believe that it is still experimental. Make sure that you read through all of the comments and understand what you are doing before making any changes. You might also consider spinning up a second scaled application to test this on before messing with your production application.
Is there any extension for chrome which is similar to Hybridfox or Elasticfox?
You can use AWS web console from Amazon to do the same things from Google Chrome.
As of now there is nothing similar to Elastifox on Google Chrome.
There is this Chrome Extension:
elastic-chrome
But it does not seem to be actively developed, sorry.
So there is Eucalyptus.
It is an abstraction layer between EC2 and your virtualized hardware. It is also an abstraction layer between physical hardware, KVM, VMWare, etc and your VM operating systems. Feasible. Unfortunately if you left VMWare for KVM, Xen, etc. for the performance gains then you are literally destroying these benefits so that your infrastructure team can assign quotas instead of provisioning things as the company needs, or actively managing environments and the costs associated with them. If you are on physical hardware then welcome to the wild world of virtualization. You should evaluate virtual Iron (Oracle VM) now since its free and you need to catch up.
Unless your infrastructure team/guy is outnumbered by your applications and development personnel by a ratio of at least 10 to 1 this is completely manageable and is supposed to be their job. Otherwise then assigning quotas would be a great idea, although it would be a decent performance drain (tell me I am wrong with references please.)
It would be worth your time to look at Chef (Puppet sucks.) Knife has EC2, KVM, VMWare, et al provisioning capabilities to spin up an entire node and everything you want on it from a simple CLI command.
As for browser extensions, there are quite a few Amazon cloud management tools available for Firefox. Unfortunately since Google and Amazon are now competing against one another there are very few quality tools for Chrome. I use Chrome as my primary browser, Firefox for tools that arent controversial, and IE/Safari when there is no other option.