Por primera vez nuestro país contará con un programa de maestría a tiempo completo, o dedicación exclusiva, en Ciencia de la Computación. La Universidad Católica San Pablo a través de la Facultad de Ingeniería y Computación, que ya ofrece el programa de pre-grado en Ciencias de la Computación tendrá a cargo el primer programa de maestría en Ciencia de la Computación gracias a financiamiento de CONCYTEC.
El Dr. Alex Cuadros, líder de este proyecto y logro para el área de computación, ha anunciado que gracias a este financiamiento del gobierno peruano los estudiantes podrán recibir un estipendio que asciende a S/. 2500 y también incluye seguro médico entre otros beneficios. Este nuevo programa, que iniciará actividades el año 2014, contará también con fondos ascendentes a S/. 100,000 anuales para dedicarlos exclusivamente a fines de investigación.
En las próximas semanas se difundirá mayor información acerca del programa y cómo postular al mismo. Una gran noticia para el país.
A bit late but I’ve created a new 4096 RSA GPG key. I’ve published a transition document as well. I hope I can meet fellow Debian developers soon to get my new key signed. So, if you are in town (Arequipa, Peru) drop me an email!
Posted in Debian
Tagged Debian, gpg
El ACM Chapter de la UCSP está organizando la primera edición del Concurso Escolar de Programación. El Concurso Escolar de Programación es una competencia que fomenta la creatividad e innovación a través del análisis y solución de problemas computacionales. Los participantes probarán sus habilidades de abstracción, diseño de algoritmos y programación en un ambiente competitivo.
El concurso se llevará a cabo el 6 y 7 de diciembre del 2013 en la Universidad Católica San Pablo – Arequipa, Perú. La modalidad de participación es individual. Esperamos que los participantes puedan obtener la experiencia necesaria para después intentar participar de las competencias internacionales como el International Olympiad in Informatics – IOI o la competencia ACM International Collegiate Programming Contest (ICPC).
Los participantes pueden registrarse y ver el reglamento del concurso en: http://cs.ucsp.edu.pe/cep2013/
First of all, I’d like to tell you that all no-computer-related experiments will be published over the no-computer website. So, this is the last post for such creations. Hope you enjoy!
Posted in Music
Cloud is passing the hype curve and we are seeing more stable developments and offerings on the market. Lately I’ve been playing with RedHat’s Openshift. Openshift is a PaaS (Platform as a Service) offering that intends to be an alternative for vendors such as Heroku. The focus for such offerings is to give developers enough flexibility and tools that handle the application deployment and maintenance process in a way that is integrated with their existing development workflow and tools.
I’ve been using Heroku for a while to deploy small to medium size projects. I liked the tools and developer-centered experience they offer. Openshift is quite new on the market and it comes in two flavors: Openshift Online, which is a PaaS service, and Openshift Enterprise, which allows organization to setup a PaaS within their own infrastructure. Both of them powered by the Openshift origin software. I’ll not compare Heroku vs. Openshift feature by feature but from my experience I can tell that Openshift is far from mature and will need to give developers more features to increase adoption.
When developing applications for Openshift developers are given a set of application stack components, similar to Heroku’s buildpacks. They call them cartridges. You can think of them as operating system packages, since the idea is the same: have a particular application stack component ready to be used by application developers. Most of the cartridges offered by the service are base components such as application server, programming language interpreters (Ruby, Python, etc), web development frameworks and data storage, such as relational and non-relational databases. Cartridges are installed inside a gear, which is a sort of application container (I believe it uses LXC internally). Unsurprisingly this Openshift component doesn’t leverage on existing packaging for RHEL 64bit, the OS that powers the service. I’d expect such things from the RedHat ecosystem.
I had to develop a cartridge to have a particular BI engine to be used as embed component by application developers. After reading docs and reference I realized this can be piece of cake, since I have packaging experience. Wrong. Well, quite so. The tricky part for Openshift Online is that it does not offer enough information on the cartridge install process so you can see what’s going wrong. To be able to see more details on the process you’ll need to setup an Openshift origin server and use it as a testing facility. Turns out that having a Origin server to operate correctly is also a challenging task and consumed a lot of my time. Over the recent weeks I’ve learned from origin developers that such features are on the road map for the upcoming releases. That’s good news.
One of the challenges I had, and still have to figure out, is that unlike the normal cartridges mine didn’t required to launch any service. Since it is a BI engine I just needed to configure and deploy to an application server such as JBoss. Cartridge format requires to have a sort of service init.d script under bin along with setup, install and configuration scripts that are ran on install. Although every day I become more familiar with origin and Openshift internals I still have work to do. Nice thing is that I was already familiar with LXC and Ruby-based applications so I could figure where things are placed and where to look for errors on origin quite easily. The cartridges are on my github account if you care to take a look and offer advice.
Openstack has been in the news recently. Despite critics and chitchat about API compatibility, lack of strong vendor, etc., there is one thing most people, if any, is not noticing. I’m going to talk from a vendor perspective rather than from community’s. The problem I see here is confusion.
To me, one of the main reasons that feeds the confusion is the lack of understanding of what Openstack really is. I’ve been involved in the free software / open source community for more than 12 years and I’ve seen many stories about how a community struggles internally and despite of that manages to release high quality software. But what I see here is a community that develops an end-user product with a governance model that involves companies as stakeholders trying to figure out how to leverage this product in a way that preserves branding and their customers loyalty. Meaning how to sell it in a way that other companies cannot.
Most people is familiar with the Linux kernel model and it’s governance. It works very well having Linus as the benevolent dictator. Even more, most contributions to Linux’s code come from vendor-sponsored developers or employees. However, the difference of this model with Openstack’s is that vendor’s interest on Linux’s development is not related to their business model or end-user product / service differentiation. That’s why the Linux Foundation government model works pretty well for the community and for vendor.
The issues that Openstack is experiencing on the market, in my opinion, are related to the fact that the stakeholders are all trying to figure out a model that will allow a end-user product to be developed by a community but also have independence on their distribution and offering differentiation to compete on the market with the other stakeholders but also with established commercial and open-source offerings. Is quite hard to become a strong vendor for an ecosystem that is actually an end-user product.