Is there a site show cloudstack source code contribution by companies like openstack community heartbeat
http://www.stackalytics.com/
Sebastien Goasguen's Update on Apache CloudStack Community Analysis will give you a sense of the contributions.
However, you won't see a lot of companies: AFAIK, Apache accepts contributions from individuals and not corporations.
This isn't a programming question, so I have posted the question on the CloudStack developers mailing list
Update: Feedback from Apache CloudStack developer mailinglist
Related
We are investigating how to integrate our app with Github Enterprise.
There are 2 different deployment models - 'Cloud' and 'On Premise'
I have been looking around but couldn't find the differences between the two.
Maybe there is no such difference
The basic difference is that GitHub Enterprise Server is software you deploy on a virtual machine you provision and control (on-premise here is a bit of a misnomer since your VM could be in AWS).
GitHub Enterprise Cloud, on the other hand, is an enterprise-level of service at GitHub.com.
You'll find more here.
I am not sure if this is a genuine question but I will try anyway.
The Kaa platform promises an open source IoT middle-ware apparently backed by a relatively large company. They suggest StackOverflow as the forum and place to ask about it, but for a few months basically no questions have been answered. Their older forum, also sounds kind of abandoned.
Does anyone have any idea why?
If not I would like to use this question/post to raise some awareness, discussion among enthusiasts, and hopefully hear the developers' voices.
I believe in an open source project it is always important to have some feeling about the state of the project, and the community behind it (which, as the company states on their website: should be vibrant) before committing some development/testing time. Kaa sounds as a great alternative for IoT projects. I would like to hear some of the opinions from other developers who are using Kaa about this issue.
Thanks!
pepgma, Mayur Patel,
Andrew Kokhanovskyi here, CTO at Kaa. First of all, please let me apologize for the lack of responses in public forums that you have experienced in the last few months. As you may know from our recent webinars, posts, etc., we are now working hard on the next version of the Kaa platform: codename "Banana Beach". It is because of the push to get the significantly improved version of Kaa to the early adopters that our engineering team has been having difficulties supporting all of the community requests lately.
Having said that, we truly appreciate your support of the Kaa open-source platform. As a token of gratitude, we would like to offer an invitation code: "AA-ADOPTER5" that you can use to register for the early access to Kaa BB here:
https://www.kaaproject.org/apply-for-early-access-to-kaa-1-0-banana-beach/
On our end, we will make sure that you will have a chance to be among the first ones to experience the new version of the Kaa platform.
--Andrew and the Kaa team
I used the Floodlight for some openflow testing but I am not totally convinced by this and I saw that OpenDaylight is sustained by Linux Foundation and some of the major industry companies.
Can someone point some strong features that OpenDaylight have and FloodLight don't ? And if someone worked with OpenDaylight could point me to some good tutorials ?
have you checked out the Wiki? There is a lot of topics there. It is still getting sorted out and what not so you may need to use the search engine to find specifics more times then not.
We have some images that are pre-built OpenStack builds. The latest is from a couple of weeks ago for the upcoming OpenStack IceHouse release.
ODL and Icehouse Integration
All in all it is still rough around the edges and has a ton of development happening still.
There are some basic mininet examples using OpenFlow and the OVSDB plugin here:
OpenFlow and Mininet
OVSDB ODL plugin:
ODL and OVSDB Plugin with Mininet
For API related apps, Fred Hsu's blog while a bit dated now has some great examples:
OpenDaylight Api App usage
If you have any other specific interests the IRC channel is a good place to interact at irc.freenode.net #opendaylight or ping us in #opendaylight-ovsdb
Cheers,
This is the best one from the opensource available
http://sdnhub.org/releases/floodlight-plus-openflow13-support/
http://www.projectfloodlight.org/projects/
Hope this will help
I've seen this question but the answers are simply not good enough. I've searched the web and could find a clear listing of the main differences.
I am particularly surprised to see contradictions in the above link, that holds only 4 short answers.
So the question is, beyond support, what are (all) the differences between Alfresco Community and Enterprise editions (for the current versions of course)?
Are there functional or technical features that available in the Enterprise edition, that are not in the community edition?
I find it strange that it's so difficult to get a clear list. Looking at the forums to find this answer is not a serious option from a business perspective.
Until now, I found this link to be useful, but it's from 2009.
In particular, I find the platform support interesting, with the community edition supporting only lamp stuff:
Linux
MySQL
Tomcat
OpenLDAP
Firefox
And the enterprise edition supporting:
Windows
SQL Server
WebLogic, WebSphere
AD/Kerberos
IE and Safari
Apparently, these features are only available in the enterprise edition:
JMX monitoring
Runtime admininstration: What's that exactly? And what's in the community edition then?
Runtime indexing consistency check and update: What's in the community edition then?
High performance and availability: How is that implemented and what's in the community edition then?
Storage policies
Open source and proprietary technology stack support: which ones exaclty? Which ones are supported in the community edition?
If anyone could guide me towards serious documentation about these differences, that would be great.
I also went through the wiki but could not find an answer to my questions in there.
differences between Enterprise and Community vary in detail from version to version and are mainly visible for administrators. We see or maintain both flavors of Alfresco in midsize to very large environments and I would say it's more or less a question of taste and budget what the best decision / edition is for you. Excellent skills in infrastructure and java are highly advisable for both editions to run Alfresco in production.
The technical differences are not as dramatic as not being able to provide very similar functionality for the users - so if you're actually in a decision you should focus on a good technical partner, the support services and maybe the fact that you only get official patches in the Enterprise subscription, not on the Community. BTW Alfresco Enterprise is not Open Source but this is not a real point of interest for most end users. You can access the code as a subscription customer but it is not public available/accessible.
The main differences in features are already named more or less:
Administration
Enterprise has more views and setting in the admin web GUI. In Community you can access most configuration only from the command line. This may be a restriction but in real live Administrators prefer the command line and scripting automation.
Enterprise lets you change some Alfresco settings during runtime (most settings still require restart). Some can be change in the GUI and more in the jmx interface. Also you're able to stop and start subsystems like the CIFS protocol server. We use this feature to switch a system in read only mode. This point is meant with "runtime admininstration". Community requires restart of the service for most configuration changes. It is possible to work around this by advanced scripting like groovy or by implementing modules.
Indexing
Runtime indexing consistency check and update is not a self healing functionality as expected. You will have to learn (at least for now) that you have to recreate the Alfresco index from time to time even in Enterprise environments and that it is better to focus on good strategies how to speed recreation or how to setup standby indexes instead of hunting failed indexing transactions using the check and update methods. For major document model changes you need to recreate the index anyway.
High performance and availability
This is mainly the cluster and replication functionality which is no longer available in Community. It's similar to MS Clusters: It's a lot, lot work for very view more availability since some concepts are missing. The price is high in terms of complexity and can end up in loss of robustness. Even with enterprise support it's a hard job to keep a alfresco cluster running - so you need very good arguments why to go this way. But of course: its possible and available!
High performance: There shouldn't be any difference and if - I'm very curious about the explanation.
Technology stack
The main difference is the database support. In the Community you only can choose between MySQL and Postgres (No Oracle or MS SQL for Community). All other technologies are independent from Enterprise or Community (AD, Kerberos, OS, Browser, ...)
Java Container: I believe over 95% of all Alfresco installations run in tomcat. That's the configuration which is documented, tested and scales. Using WebLogic or WebSphere gives you no added value except new challenges - quite the contrary: You have to solve most issues for yourself and can't benefit from others experience.
Storage policies: I'm not pretty sure and should check in 4.2.x if the Content Store Selector / Storage policies is no longer available in the Community, but it was there in the 3.x versions.
[Edit]: storage policies have been removed in Community 4.2.x:
NoSuchBeanDefinitionException: No bean named 'storeSelectorContentStoreBase' is defined
If there is a really need for this functionality someone may re-enable that feature by coding a module for Community.
Regards
This page explains the difference between the editions:
https://wiki.alfresco.com/wiki/Enterprise_Edition
This page is the canonical, comprehensive list of the differences.
If you are considering an Enterprise Subscription and you have a question that isn't answered by what you can find on that page, you should talk to your account rep.
Well, regarding JMX monitoring:
Runtime administration: Alfresco enterprise allows to perform certain actions on Alfresco subsystems without restarting the server. This allows you to be very fast during debugging/developing and also making changes in production environment. Also you can access the JMX interface that supports JMX Remoting.
There is no consistency check or update, until you restart the server (during the startup you have to validate/check/rebuild your indexes). There is an option in alfresco.global.properties (or the original repository.properties config file) for that. If you have some inconsistencies in the Alfresco Community index, you're gonna have a bad time xD.
Alfresco Enterprise has specific license for clustering your architecture, the Community edition doesn't support those systems. Replicate and cluster Alfresco is one of the main improvements in performance/scalability/availability you could achieve.
The storage policies allow you to use Content Store selectors in Alfresco Enterprise. You can manage a primary and a secondary file store, and map/connect these stores in your architecture. The Community Edition allows you only to use one content store at a time.
These include everything inside Alfresco (Spring Framework, Apache-Lucene/Solr, Tomcat, and so on), because with the Enterprise license you have also the full support with everything inside the Alfresco package. The difference is that the Community is based on daily builds, supported by community, and therefor not guaranteed. The Enterprise support helps you resolve many problems that you might encounter during developing and in production environment, not only Alfresco related, but also on some configurations on supported platforms (Windows/Linux), your web application servers, and so on.
Hope it helps.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
Improve this question
I'm operating a neighbourhood WIFI network in a rural environment.
Now I'm looking fo a monitoring tool to run on a server (Windows or Linux) which would track bandwidth, uptime (clients as well as internet connection), etc...
Most of this information is exposed via SNMP by my routers and access points, so SNMP support is required.
Additional features should be:
Graphical data representation
free license
So what's the best choice for me?
Edit These are the tools mentioned so far:
MRTG
Munin
Nagios
Zenoss Core
ntop
cacti
ZABBIX
MRTG is probably the easiest to setup. If your router has SNMP (as you mention), to setup it's a single command:
cfgmaker --output=mrtg_myrouter.cfg public#1.2.3.4
MRTG is good for high-bandwidth routers and the likes. It's not great for other data (it can be coerced into graphing most things, but it's a little unintuitive to setup)
For monitoring other stuff I like Munin. I would describe it again, but I posted an answer a while ago here (about graphing disc-usage).
Munin can of course graph network usage, and easily pull data via SNMP (in fact it's the recommended setup for grabbing data from Windows-based servers - run a SNMP daemon on the Windows machine, and have Munin connect to this). The graphs are also prettier than MRG, I would say (clearly the most important factor..)
There's an example installation of MRTG here, and Munin here
IMHO, Cacti is easiest to install and use.
Zabbix is interesting, but harder to use.
And here is a very comprehensive list of all network monitoring tools.
Not sure if this fits your usage but a lot of web hosting provider uses Nagios for network monitoring
Zenoss Core is free and open source. It keeps RRD graphs (like other monitoring tools mentioned here). To monitor parameters other than basic network bandwidth (and up state), the switch or router SNMP definitions and MIBs should be available as a ZenPack. Runs on a Linux (virtual?) server. Uses Google Maps to display link status.
I have been using ntop it is free on linux and for purchase if you want a windows binary and worked pretty well for us
I had the same question last week and tried several options.
For basic snmp graphing needs, cacti is great, but graphing apache, mysql, etc. is a bit too hard I think.
ntop is also a nice tool, but has a different usecase than the other ones in your list.
You should look at Zenoss. The Core version is FOSS, userfriendly, and very powerful. I had no need for the Enterprise version, but your needs may differ.
It does graphing, monitoring and alerting of all the basic stats, but download some ZenPacks and you can easily add Apache, MySQL or many other stats. All configuration can be done via the GUI. The interface is clear and responsive and allows for easy management of very large networks.
In short, I'm glad I never spent much time on Nagios, because I believe Zenoss is the best option available.
Also consider CactiEZ on a VM or small server, it is a baremetal CentOS 6 based system.