Skip to main content

Home/ Arquitectura?/ Group items tagged deployment

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Pablo Lalloni

Dogtag - 1 views

www.dogtagpki.org/...PKI_Main_Page

infrastructure tools operations security pki ca ocsp architecture certificates certificate-management

shared by Pablo Lalloni on 08 Jan 19 - No Cached
  • Pablo Lalloni on 08 Jan 19
     
    "The Dogtag Certificate System is an enterprise-class open source Certificate Authority (CA). It is a full-featured system, and has been hardened by real-world deployments. It supports all aspects of certificate lifecycle management, including key archival, OCSP and smartcard management, and much more. The Dogtag Certificate System can be downloaded for free and set up in less than an hour."
Pablo Lalloni

Terrier IR Platform - Homepage - 0 views

www.terrier.org

development programming perceptual-hashing image-recognition audio-recognition image-indexing image-searching

shared by Pablo Lalloni on 12 Apr 18 - Cached
  • Pablo Lalloni on 12 Apr 18
     
    "Terrier is a highly flexible, efficient, and effective open source search engine, readily deployable on large-scale collections of documents. Terrier implements state-of-the-art indexing and retrieval functionalities, and provides an ideal platform for the rapid development and evaluation of large-scale retrieval applications."
Pablo Lalloni

Deliver Your Java Application in One-JAR™ ! - 0 views

one-jar.sourceforge.net

java jar tools deployment development jvm package

shared by Pablo Lalloni on 04 May 12 - Cached
  • Pablo Lalloni on 04 May 12
     
    One-JAR lets you package a Java application together with its dependency Jars into a single executable Jar file.
Pablo Lalloni

[#AS7-3719] Grails app load with Jboss 7 - JBoss Issue Tracker - 0 views

issues.jboss.org/AS7-3719

grails jboss deployment issues

shared by Pablo Lalloni on 27 Jun 12 - No Cached
    • Pablo Lalloni
      Pablo Lalloni on 27 Jun 12
       
      Aparentemente en los comments de mas abajo hay una solución propuesta por Graeme Rocher para deployar correctamente aplicaciones Grails en JB7+
    • Pablo Lalloni
      Pablo Lalloni on 27 Jun 12
       
      Marqué el comentario relevante con amarillo.
  • Hide Permalink Graeme Rocher added a comment - 19/Mar/12 12:52 PM Building the Grails war with: grails -Dgrails.project.war.osgi.headers=false war Will remove the OSGi headers from the WAR file which is what is confusing JBoss 7. The above can also be configured in BuildConfig.groovy
Pablo Lalloni

Microservices and PaaS - Part I | ActiveState - 0 views

www.activestate.com/...microservices-and-paas-part-i

development programming cloud-computing microservices architecture software-architecture software-engineering

shared by Pablo Lalloni on 25 Aug 14 - No Cached
  • Instead of building software that resembles our existing organizations, we should figure out how we want our software to look, then build the organization around that. Or reorganize it if it's already in place.
    • Pablo Lalloni
      Pablo Lalloni on 25 Aug 14
       
      Las implicancias de esta idea en nuestra organización...
  • When deploying a new feature, enhancing or fixing an existing capability, or deploying an experimental line of code, the previous code remains available and accessible. New code is deployed alongside the old code, with mechanisms in place to instantly route to one or another version.
  • Importantly, the old code is not replaced, but remains part of the system, and is kept running. If, as is often the case, the widespread introduction of the new feature results in unforeseen consequences, the feature flag can be toggled off, and the old version is instantly used instead.
  • ...13 more annotations...
  • In a microservices architecture, an application is comprised of a number of small, independent composable services that interact by way of an external published protocol, such as REST, or a messaging service.
  • Each service is focused on an individual targeted business capability, and thus its scope is minimized. For functionality out of scope, the microservice calls out to other microservices via the published protocol.
  • Small independent microservices can be built using the technology best suited for their requirements. No longer does every application component need to be built on a common company-mandated language and framework such as Java/Spring or Ruby on Rails.
  • Similarly, there's no reason to standardize on a single persistence layer across an entire application. Some microservices might best be served by Redis, others by Oracle.
  • Each microservice can be updated independently, no longer requiring the entire application to be redeployed.
  • Microservices drastically improve the time required to push out a new update, allowing a much more agile development process.
  • Many organizations consist of specialized silo teams (UI, database, API, etc) where costly handoffs and intercommunication are required to coordinate all the pieces of application construction. These handoffs cause overhead, and the need for them should be eliminated.
  • With small teams, each focused on an individual microservice, Netflix enables developers to push code to production, instead of getting mired in a complex deployment process involving several teams.
  • With microservices, the old IT mindset just doesn't work.
  • A centralized IT department cannot possibly cover the wide array of technologies spanning all microservices.
  • Instead a DevOps structure, where each team is responsible for the management of the corresponding microservice, is essential.
  • Enable developers to concoct systems of their choosing with minimal or no interaction from IT, management, VPs, hardware or other groups. "Self Service" is one of the major capabilities offered by the cloud and there's every reason to take advantage of this.
  • Now, IT can be considered as a cloud API available to the developer on-demand 24x7, instead of a complex, process-mired division hidden behind obscure process.
Pablo Lalloni

Microservices and PaaS - Part II | ActiveState - 0 views

www.activestate.com/...microservices-and-paas-part-ii

development programming cloud-computing microservices architecture software-architecture software-engineering operations devops

shared by Pablo Lalloni on 25 Aug 14 - No Cached
  • All aspects of deployment, monitoring, testing, and recovery must be fully automated.
  • Refactor database schemas, and de-normalize everything, to allow complete separation and partitioning of data.
  • There should be no sharing of underlying tables that span multiple microservices, and no sharing of data. Instead, if several services need access to the same data, it should be shared via a service API (such as a published REST or a message service interface).
    • Pablo Lalloni
      Pablo Lalloni on 25 Aug 14
       
      Aleluya!
  • ...5 more annotations...
  • Instead each microservice should have its own scm repository so it can truly be updated and enhanced independent of other services.
  • Gone are the days of a single monolithic database instance that's shared across all parts of an application.
  • Each microservice must have its own manifest and dependencies, instead of maintaining a global dependency list for all services.
  • Containerization brings countless advantages, particularly a consistent, isolated runtime environment that can easily migrate around the datacenter or around the globe. With Docker and other modern containerization approaches, there is very little overhead in running in a container, and considerable upside.
  • Do not build stateful services. Instead, maintain state in a dedicated persistence service, or elsewhere.
Pablo Lalloni

Red Hat Advances Enterprise Virtualization Platform With RHEV 3.4 - 2 views

www.eweek.com/...on-platform-with-rhev-3.4.html

infrastructure cloud-computing operations devops development tools docker paas redhat rhev

shared by Pablo Lalloni on 19 Jun 14 - No Cached
  • RHEV and Docker provide fundamentally different use cases, Herold explained.  "In fact, we see opportunities for RHEV to run the operating systems, including Atomic Hosts, that ultimately run Docker instances," he said. "Within the oVirt upstream project, we have an initial Docker integration to run Docker instances in VM containers provided by RHEV."
    • Pablo Lalloni
      Pablo Lalloni on 19 Jun 14
       
      Creo que la estrategia de integración de Docker de RH está equivocada. Siguiéndola obtienen la mitad de los beneficios de Docker (agilidad de empaquetamiento, distribución y deployment) pero dejan de lado la otra mitad (mucho mayor performance y eficiencia de un container versus una vm) que muchos competidores sí ofreceran a sus clientes, abriendo una brecha.
Pablo Lalloni

CoreOS is Linux for Massive Server Deployments - 2 views

coreos.com

linux docker cloud os server infrastructure cloud-computing coreos containers fleet etcd systemd

shared by Pablo Lalloni on 23 Jun 14 - No Cached
  • Pablo Lalloni on 23 Jun 14
     
    "CoreOS is a Linux distribution that has been rearchitected to provide features needed to run modern clustered infrastructure stacks. The strategies and architectures that influence CoreOS allow companies like Google, Facebook and Twitter to run their services at scale with high resilience. We've implemented them correctly so you don't have to endure the slow, learn-as-you-go infrastructure building process. CoreOS can run on your existing hardware or on most cloud providers. Clustering works across platforms, making it easy to migrate parts of your gear over to CoreOS, or to switch cloud providers while running CoreOS."
Pablo Lalloni

spotify/helios - 0 views

github.com/helios

docker deployment development programming tools cloud-computing operations devops

shared by Pablo Lalloni on 13 Aug 14 - No Cached
  • Pablo Lalloni on 13 Aug 14
     
    "Helios is a Docker orchestration platform for deploying and managing containers across an entire fleet. [...] We at Spotify are running this in production now (as of early July 2014) with a money-generating service, so we trust it. Whether you should trust it to not cause smoking holes in your infrastructure is up to you."
Pablo Lalloni

GoogleCloudPlatform/kubernetes - 0 views

github.com/...kubernetes

development tools cloud-computing operations docker google kubernetes devops paas deployment

shared by Pablo Lalloni on 13 Aug 14 - No Cached
  • Pablo Lalloni on 13 Aug 14
     
    "Kubernetes is an open source implementation of container cluster management. Kubernetes is in pre-production beta! While the concepts and architecture in Kubernetes represent years of experience designing and building large scale cluster manager at Google, the Kubernetes project is still under heavy development. "
Pablo Lalloni

Tsuru - 0 views

www.tsuru.io

deployment development programming tools cloud-computing operations devops paas docker tsuru

shared by Pablo Lalloni on 13 Aug 14 - No Cached
  • Pablo Lalloni on 13 Aug 14
     
    "Tsuru is an extensible and open source Platform as a Service software. Deploy Fast and secure. The entire process is really simple with no special tools needed, just a simple git push. Scale Scaling in Tsuru is completely painless. Just add a unit and Tsuru will take care of everything else. Extend Tsuru is built to be extensible. Through services you can provide anything your application needs."
Pablo Lalloni

Deis - 0 views

deis.io/overview

docker development programming deployment tools paas devops operations cloud-computing deis

shared by Pablo Lalloni on 13 Aug 14 - No Cached
  • Pablo Lalloni on 13 Aug 14
     
    "Deis (pronounced DAY-iss) is an open source PaaS that makes it easy to deploy and manage applications on your own servers. Deis builds upon Docker and CoreOS to provide a lightweight PaaS with a Heroku-inspired workflow. Deis can deploy any application or service that can run inside a Docker container. In order to be scaled horizontally, applications must follow Heroku's 12-factor methodology and store state in external backing services."
‹ Previous 21 - 39 of 39
Showing 20▼ items per page